From: Loic Prylli <loic@myri.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: David Miller <davem@davemloft.net>,
jeffrey.t.kirsher@intel.com, netdev@vger.kernel.org,
jeff@garzik.org, peter.p.waskiewicz.jr@intel.com,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] pciaer: report config read/write errors
Date: Tue, 02 Dec 2008 15:14:35 -0500 [thread overview]
Message-ID: <4935972B.8050608@myri.com> (raw)
In-Reply-To: <20081202114441.4389fab7@extreme>
On 12/02/2008 02:44 PM, Stephen Hemminger wrote:
> pci_find_ext_capability would succeed but all access to registers >= 256
> would fail if MMCONFIG failed.
Your sentence seems self-contradicting to me. pci_find_ext_capability()
(!= pci_find_capability()) only tries to access registers >= 256, so I
don't see how it would succeed if *all* those accesses are failing.
> P.s: you can look back into LKML for Linus discussion about why MMCONFIG
> is broken anyway.
>
I was an active participant in one of those discussions (although it is
possible I missed a later one), so I am quite aware about the
limitations of MMCONFIG. But pci_find_ext_capability() looked to me a
good filter to check about those limitations().
This is not just about pciaer, for instance, it might be that a lot of
the SR-IOV code submitted recently assumes that if the corresponding
extended-capability can be detected, little checking needs to be done
afterwards.
Loic
next prev parent reply other threads:[~2008-12-02 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 0:41 [NET-NEXT PATCH] ixgbe: Implement PCIe AER support Jeff Kirsher
2008-12-02 1:47 ` Stephen Hemminger
2008-12-02 7:25 ` David Miller
2008-12-02 17:23 ` [PATCH] pciaer: report config read/write errors Stephen Hemminger
2008-12-02 18:41 ` Waskiewicz Jr, Peter P
2008-12-02 19:04 ` Loic Prylli
2008-12-02 19:44 ` Stephen Hemminger
2008-12-02 20:14 ` Loic Prylli [this message]
2008-12-02 21:41 ` Stephen Hemminger
2008-12-09 7:13 ` [NET-NEXT PATCH] ixgbe: Implement PCIe AER support Waskiewicz Jr, Peter P
2008-12-02 8:19 ` Waskiewicz Jr, Peter P
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=4935972B.8050608@myri.com \
--to=loic@myri.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).