From: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
To: "Greg KH" <greg@kroah.com>, <benh@kernel.crashing.org>
Cc: <linux-kernel@vger.kernel.org>, "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Subject: RE: [PATCH] PCI Express Advanced Error Reporting Driver
Date: Fri, 11 Mar 2005 10:24:15 -0800 [thread overview]
Message-ID: <C7AB9DA4D0B1F344BF2489FA165E5024080392EC@orsmsx404.amr.corp.intel.com> (raw)
On Thursday, March 10, 2005 9:23 PM Greg KH wrote:
>> On Thu, Mar 10, 2005 at 03:04:18PM -0800, long wrote:
>> PCI Express error signaling can occur on the PCI Express link itself
>> or on behalf of transactions initiated on the link. PCI Express
>> defines the Advanced Error Reporting capability, which is implemented
>> with a PCI Express advanced error reporting extended capability
>> structure, to provide more robust error reporting. With the Advanced
>> Error Reporting capability a PCI Express component, which detects an
>> error, can send an error message to the Root Port associated with
>> its hierarchy.
>This patch was too big for lkml, and should also be sent to the
>linux-pci list. Care to split it up and resend it?
Will split it up and resend.
> Also, how does this tie into the recent discussion about pci error
> recovery?
The standard PCI Specification calls out SERR and PERR. I am not sure
about the recent discussion of PCI error of recovery. It is perhaps
regarding the possibility of recovering from a PERR or SERR. However,
PCI Express error occurs on the PCI Express link or on behalf of
transactions occurred on the PCI Express link. PCI Express component,
which implements PCI Express Advanced Error Reporting Capability, sends
error message to the Root Port to indicate error occurred on the PCI
Express link where it is connected. The PCI Express error recovery is on
behalf of attempting to do a PCI Express link recovery, not PCI error
recovery. It appears that PCI Express AER is disjoint from PCI error
recovery.
Thanks,
Long
next reply other threads:[~2005-03-11 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 18:24 Nguyen, Tom L [this message]
2005-03-11 22:49 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2005-03-14 20:16 Nguyen, Tom L
[not found] <200503102304.j2AN4INc018805@snoqualmie.dp.intel.com>
2005-03-11 5:23 ` 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=C7AB9DA4D0B1F344BF2489FA165E5024080392EC@orsmsx404.amr.corp.intel.com \
--to=tom.l.nguyen@intel.com \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®