From: Linas Vepstas <linasvepstas@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Richard Lary <rlary@us.ibm.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/3] Support for PCI Express reset type
Date: Sat, 1 Aug 2009 17:40:27 -0500 [thread overview]
Message-ID: <3ae3aa420908011540k10004997o130c42cec0ba911e@mail.gmail.com> (raw)
In-Reply-To: <87hbws3jvx.fsf@basil.nowhere.org>
Hi Andi,
2009/7/31 Andi Kleen <andi@firstfloor.org>:
> Mike Mason <mmlnx@us.ibm.com> writes:
>>
>> These patches supersede the previously submitted patch that
>> implemented a fundamental reset bit field.
>>
>> Please review and let me know of any concerns.
>
> Any plans to implement that for x86 too? Right now it seems to be a PPC
> specific hack.
I've found the PCIE chipsepc somewhat daunting, but was under the
impression that much if not most of what was needed was specified
there.
See, for example:
Documentation/PCI/pcieaer-howto.txt
which states:
||| The PCI Express Advanced Error Reporting Driver Guide HOWTO
||| T. Long Nguyen <tom.l.nguyen@intel.com>
||| Yanmin Zhang <yanmin.zhang@intel.com>
||| 07/29/2006
[..]
||| The PCI Express AER driver provides the infrastructure to support PCI
||| Express Advanced Error Reporting capability. The PCI Express AER
||| driver provides three basic functions:
|||
||| - Gathers the comprehensive error information if errors occurred.
||| - Reports error to the users.
||| - Performs error recovery actions.
I presume the last bullet point means that the AER code works and
actually does more or less the same thing as the PPC EEH code,
but in a more architecture-independent way, as it only assumes
that PCI AER is there (and is correctly implemented in the CPI chipset)
The AER code uses the same core infrastructure as the EEH code,
at the time, I did exchange emails w/ the above authors discussing
this stuff.
As to whether the x86 server vendors are actually selling something
with AER in it, and whether any of them are actually testing this stuff
is unclear.
FWIW IBM has pretty much no incentive to lobby other server vendors
to get on the ball ...as this is viewed as one of those things that lets
IBM charge premium prices for PPC hardware.
--linas
next prev parent reply other threads:[~2009-08-01 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 22:33 [PATCH 1/3] Support for PCI Express reset type Mike Mason
2009-07-31 16:19 ` Andi Kleen
2009-07-31 16:47 ` Andrew Vasquez
2009-08-01 22:40 ` Linas Vepstas [this message]
2009-08-01 22:43 ` Linas Vepstas
2009-08-14 16:54 ` Jesse Barnes
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=3ae3aa420908011540k10004997o130c42cec0ba911e@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rlary@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).