lkml.org 
[lkml]   [2006]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Ordering between PCI config space writes and MMIO reads?
    On Tue, Oct 31, 2006 at 03:34:47PM -0500, Richard B. Johnson wrote:
    > If you write to the PCI bus and then you read the result, the read
    > __might__ be the
    > read that flushes any posted writes rather than the read of device

    Config space writes aren't posted, they're delayed. So, for example,
    you can do the config write on the primary bus, then it hits a bridge on
    its way to the destination device. The bridge is entitled (obviously,
    it's unlikely to) drop it, and then the config read can pass by the
    config write.

    I'm beginning to think Michael Tsirkin has the only solution to this
    -- architectures need to check that their hardware blocks until the
    config write completion has occurred (and if not, simulate that it has
    in software).

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-10-31 21:49    [W:3.379 / U:0.028 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site