From: Grant Grundler <grundler@parisc-linux.org>
To: Michael Chan <mchan@broadcom.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
akpm@osdl.org, greg@kroah.com, "Durairaj,
Sundarapandian" <sundarapandian.durairaj@intel.com>
Subject: Re: [PATCH] pci-mmconfig fix for 2.6.9
Date: Fri, 12 Nov 2004 15:31:59 -0700 [thread overview]
Message-ID: <20041112223159.GC8828@colo.lackof.org> (raw)
In-Reply-To: <B1508D50A0692F42B217C22C02D84972020F3C9D@NT-IRVA-0741.brcm.ad.broadcom.com>
On Fri, Nov 12, 2004 at 01:49:18PM -0800, Michael Chan wrote:
> I disagree with your interpretations of the ECN.
Yeah - I think the alternatives suggested in the new Implementation
Note are confusing and distracting from the actual definitions
and declarations in the previous parts of the spec. The Implementation
Note is NOT the spec. It's just advisory.
The ECN starts out by defining two classes of systems:
| Make the Enhanced Configuration Access Mechanism required for
| PC-compatible platforms, but optional for platforms based on other
| processor/system architectures where firmware abstractions are
| provided for the configuration space access (e.g., DIG64 compliant systems).
The last phrase "where firmware abstractions" is the key bit.
> 2. mmconfig implementation must provide a method for software to
> guarantee that the config access has completed before software execution
> continues.
Agreed.
> In Implementation Note, it provides some examples on how to
> do this. One example is to make mmconfig non-posted. But there are other
> examples.
Yes, but the patch only modifies code for arches which use
direct access to generate the mmconfig cycles. I believe the
posted write examples are for systems which provide "an architected
firmware interface". I'm pretty sure "software" in this context
refers to the "firmware" (e.g. SAL). This spec wasn't written exclusively
for OS dorks like us.
> 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.
hth,
grant
next prev parent reply other threads:[~2004-11-12 22:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 21:49 [PATCH] pci-mmconfig fix for 2.6.9 Michael Chan
2004-11-12 22:31 ` Grant Grundler [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-15 7:07 Michael Chan
2004-11-15 8:01 ` Grant Grundler
2004-11-13 16:22 Michael Chan
2004-11-13 19:46 ` Grant Grundler
2004-11-14 8:58 ` Andi Kleen
2004-11-15 6:00 ` Grant Grundler
2004-11-15 8:33 ` Andi Kleen
2004-11-12 23:56 Michael Chan
2004-11-13 9:22 ` Andi Kleen
2004-11-12 19:23 Michael Chan
2004-11-12 20:55 ` Grant Grundler
2004-11-12 17:52 Michael Chan
2004-11-12 18:35 ` Grant Grundler
2004-11-11 16:33 Nguyen, Tom L
2004-11-10 22:20 long
2004-11-11 1:30 ` Greg KH
2004-11-11 7:57 ` Andi Kleen
2004-11-10 19:38 long
2004-11-10 19:35 ` Greg KH
2004-11-10 17:26 Durairaj, Sundarapandian
2004-11-10 17:35 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041112223159.GC8828@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mchan@broadcom.com \
--cc=sundarapandian.durairaj@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox