lkml.org 
[lkml]   [2009]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [BUG FIX] Make x86_32 uni-processor Atomic ops, Atomic
    Date
    On Fri May 22 2009, Andi Kleen wrote:
    > On Fri, May 22, 2009 at 01:43:27PM -0500, Michael S. Zick wrote:
    > > On Fri May 22 2009, you wrote:
    > > > "Michael S. Zick" <lkml@morethan.org> writes:
    > > >
    > > > > Found in the bit-rot for 32-bit, x86, Uni-processor builds:
    > > >
    > > > Actually uni processor should not use the lock prefix
    > > > because it doesn't need it; the only exception are some special
    > > > ops used in para-virtualization which are special cased.
    > > >
    > >
    > > Unless you have interrupts enabled, then you have two contexts.
    >
    > Interrupts on the local CPU don't interrupt instructions, only
    > inbetween.
    >

    Ref: http://developer.intel.com/Assets/PDF/manual/253666.pdf
    Manual page: 3-590 PDF page: 638
    Summary: Processors prior to P-4 can take an interrupt between
    the read cycle and the write cycle. Which is why opcode 0xF0 exists.

    Mike

    > -Andi




    \
     
     \ /
      Last update: 2009-05-22 21:55    [W:0.021 / U:184.296 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site