mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-pci@atrey.karlin.mff.cuni.cz
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>
Subject: Error reporting API, any work in progress ?
Date: Wed, 02 Feb 2005 13:11:43 +1100	[thread overview]
Message-ID: <1107310304.5624.56.camel@gaston> (raw)

Hi !

Is there any work in progress to get some unified error reporting (and
possibly recovery) API for PCI/X/e ?

On pSeries, we have this "EEH" mecanism that allows us, even with
old-style PCI, to get error notification, but also to recover by doing
slot reset and that sort of stuff.

PCI Express has error reporting at least, IBM's implementation will have
similar reset control for recovery.

So I think we should need some generic error reporting capability to be
added to the PCI layer, possibly by adding a function pointer to
pci_driver() that gets called back to report various events, in addition
to the proposed explicit error checking that can bracket IO calls like
it was discussed a while ago on lkml.

In addition, I was thinking about some generic routines the drivers
could call to indicate, upon such errors, that they are willing to
recover after a slot reset. That way, the platform can notify all
drivers of a bus segment that went off, reset the slot, and send
messages to those drivers telling them the slot is back.

If there is already some work in progress for that (PCI driver-level API
for notification), I'd be happy to help there. If not, then I'll propose
something that would fit the need of IBM EEH mecanism and PCI express.

Ben.



                 reply	other threads:[~2005-02-02  2:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1107310304.5624.56.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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®