From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: wendyx@linux.vnet.ibm.com, Auke Kok <auke-jan.h.kok@intel.com>,
jeff@garzik.org, e1000-devel@lists.sourceforge.net,
netdev@vger.kernel.org, Kumar Gala <galak@kernel.crashing.org>,
Wen Xiong <wenxiong@us.ibm.com>
Subject: Re: [PATCH] e1000: Work around 82571 completion timout on Pseries HW
Date: Sat, 23 Jun 2007 10:05:08 -0700 [thread overview]
Message-ID: <467D52C4.6010905@intel.com> (raw)
In-Reply-To: <20070623082003.GA29471@infradead.org>
Christoph Hellwig wrote:
> On Thu, May 17, 2007 at 09:58:03AM -0500, Wen Xiong wrote:
>>>> It really shouldn't be there at all because something in either the
>> intel
>>>> or pseries hardware is totally buggy and we should disable features in
>>>> the buggy one completely.
>> Hi,
>>
>> Here there are not hardware issue on both Intel or PPC. The patch is to
>> work around a loop hold on early version of PCI SGI spec.
>> The later PCI Sgi have spec have corrected it. We can just implement it
>> for PPC only. Other vendor may have the same issue.
>
> In this case we should add a blacklist for implementations of the old
> spec. There should be a way to find specific bridges in the OF firmware
> tree on powerpc and similar things on other platforms aswell.
Yes, this is almost what we did.
IBM is currently testing my patches that implement a generic pci quirk that will
be enabled for only selected root complex ID's that require the (1.0a spec)
device to disable the completion timeouts.
They are currently validating this test on the affected hardware. I expect to
get the results within a week and then I will post the patch.
Since this is one of the few holes in between the two specs (where manual
intervention is needed) I think that a single quirk is a fairly sane approach.
Cheers,
Auke
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-23 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 8:53 [PATCH] e1000: Work around 82571 completion timout on Pseries HW Auke Kok
2007-05-16 16:00 ` Jeff Garzik
2007-05-16 22:11 ` Wen Xiong
2007-05-16 22:31 ` Benjamin Herrenschmidt
2007-05-17 0:43 ` Kumar Gala
2007-05-17 9:01 ` Christoph Hellwig
2007-05-17 13:10 ` Kumar Gala
2007-05-17 14:58 ` Wen Xiong
2007-05-17 21:04 ` Jeff Garzik
2007-05-17 21:44 ` wendy xiong
2007-06-23 8:20 ` Christoph Hellwig
2007-06-23 17:05 ` Kok, Auke [this message]
2007-05-18 0:47 ` Jeff Garzik
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=467D52C4.6010905@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=galak@kernel.crashing.org \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=wendyx@linux.vnet.ibm.com \
--cc=wenxiong@us.ibm.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).