mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: "Greg KH" <greg@kroah.com>, <benh@kernel.crashing.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] PCI Express Advanced Error Reporting Driver
Date: Sat, 12 Mar 2005 09:49:02 +1100	[thread overview]
Message-ID: <16946.8286.720245.664510@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <C7AB9DA4D0B1F344BF2489FA165E5024080392EC@orsmsx404.amr.corp.intel.com>

Nguyen, Tom L writes:

> 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.

To give you some context, the recent discussion was about how we could
give a unified interface to drivers for both PCI-Express error
reporting and for the "Enhanced Error Handling" (EEH) facilities we
have on IBM PPC64 boxes.  EEH includes not only the detection and
reporting of errors (for PCI, PCI-X and PCI-Express buses) but also
hardware support for isolating devices when an error is detected, plus
means for resetting individual bus segments or slots, to assist in
recovering a device which has got into a bad state.

Does PCI Express provide any facilities for recovering from errors,
beyond just "try that transaction again"?

Paul.

  reply	other threads:[~2005-03-11 23:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 18:24 Nguyen, Tom L
2005-03-11 22:49 ` Paul Mackerras [this message]
  -- 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=16946.8286.720245.664510@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.l.nguyen@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

all inboxes | Powered by JetHome®