lkml.org 
[lkml]   [2008]   [Jun]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: MMIO and gcc re-ordering issue
    On Tue, Jun 03, 2008 at 11:47:00AM -0700, Trent Piepho wrote:
    > On Tue, 3 Jun 2008, Linus Torvalds wrote:
    > >On Tue, 3 Jun 2008, Nick Piggin wrote:
    > >>
    > >>Linus: on x86, memory operations to wc and wc+ memory are not ordered
    > >>with one another, or operations to other memory types (ie. load/load
    > >>and store/store reordering is allowed). Also, as you know, store/load
    > >>reordering is explicitly allowed as well, which covers all memory
    > >>types. So perhaps it is not quite true to say readl/writel is strongly
    > >>ordered by default even on x86. You would have to put in some
    > >>mfence instructions in them to make it so.
    >
    > So on x86, these could be re-ordered?
    >
    > writel(START_OPERATION, CONTROL_REGISTER);
    > status = readl(STATUS_REGISTER);

    You wouldn't ask for write-combining memory mapping for control or
    status registers.

    > >Well, you have to ask for WC/WC+ anyway, so it's immaterial. A driver that
    > >does that needs to be aware of it. IOW, it's a non-issue, imnsho.
    >
    > You need to ask for coherent DMA memory too.

    Different case. Coherent DMA memory is *host* memory that the *device*
    accesses. We're talking about *device* memory that the *cpu* accesses.

    --
    Intel are signing my paycheques ... these opinions are still mine
    "Bill, look, we understand that you're interested in selling us this
    operating system, but compare it to ours. We can't possibly take such
    a retrograde step."


    \
     
     \ /
      Last update: 2008-06-03 20:59    [W:0.020 / U:61.636 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site