[lkml]   [2004]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRE: [PATCH] pci-mmconfig fix for 2.6.9
    On Fri, 12 Nov 2004, 15:31:59 -0700, Grant Grundler wrote:

    > On Fri, Nov 12, 2004 at 01:49:18PM -0800, Michael Chan wrote:
    > > In short, I believe mmconfig is allowed to be posted or
    > non-posted. If
    > > it is posted, there must be a method to allow software to flush it.
    > Yes. Agreed.
    > But existing direct access methods must implement
    > non-postable writes to be compliant.
    > E.g. the second paragraph of the Implementation Note:
    > | In those cases in which the software must know that a posted
    > | transaction is completed by the completer, ...
    > IMHO, "In those cases" refers to the second class of systems.
    > i386 and x86_64 are (still) in the first class of "legacy" systems.

    Hi Grant,

    I think we are almost in agreement. IMHO, the entire ECN applies the
    PC-compatible systems and any examples in the Implementation Note is a
    valid implementation. mmconfig can be posted, as long as there is a way
    to guarantee that the write has completed, such as flush by reading. We
    disagree on this point.

    The Intel mmconfig implementation is non-posted which is a valid
    implementation. Therefore readl is unnecessary and can be removed.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:08    [W:0.048 / U:4.420 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site