Subj : Re: What is the real costs of LOCK on x86 multiprocesor machine?
To   : comp.programming.threads
From : chris noonan
Date : Sun Jul 31 2005 06:26 am


David Schwartz wrote:
> "chris noonan" wrote

> > I vaguely remember encountering the LOCK prefix
> > in one or two places in Microsoft OS code disassembly
> > (uniprocessor installation). I assumed it was simply
> > a mistake, something like new routines being hacked
> > in quickly without them taking the trouble to add
> > the offsets of the LOCK prefixes to the list to be
> > NOP'ed out.
>
>     By the way, the way I do this in applications is by using an illegal
> instruction. I catch the fault and replace the illegal instruction with
> either a LOCK or  NOP at run time.
>
>[code snipped]

Ingenious. I wonder if there might be a way of doing
this for Microsoft Windows?

Chris

.