From: linas@austin.ibm.com (Linas Vepstas)
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Rajesh Shah <rajesh.shah@intel.com>,
Yanmin Zhang <yanmin.zhang@intel.com>,
linux-pci maillist <linux-pci@atrey.karlin.mff.cuni.cz>,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org
Subject: Re: pci error recovery procedure
Date: Tue, 12 Sep 2006 14:38:57 -0500 [thread overview]
Message-ID: <20060912193857.GB29167@austin.ibm.com> (raw)
In-Reply-To: <1157599136.20092.529.camel@ymzhang-perf.sh.intel.com>
On Thu, Sep 07, 2006 at 11:18:56AM +0800, Zhang, Yanmin wrote:
> The error recovery procedures
> are to process pci hardware errors instead of device driver bug.
Over the last three years, we've uncovered (and fixed) dozens of
device driver bugs that were only detected because of the pci error
detection hardware. The ability to get device dumps is important,
because many of these bugs are hard to reproduce, require getting
PCI bus analyzers attached to the system, etc.
> Current error handler infrastructure could support pci-e, but I want a better
> solution to faciliate driver developers to add error handlers more easily. My
> startpoint is driver developer. If they are not willing to add error handlers,
> it's impossible to do so for all drivers by you and me.
Right. As a result, we only care about the products that we actually
sell to customers. PCI error recovery is not some "gee its nice" piece
of eye-candy or chrome: either one is serious about high-availability,
or one is not.
--linas
prev parent reply other threads:[~2006-09-12 19:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1157008212.20092.36.camel@ymzhang-perf.sh.intel.com>
[not found] ` <20060831175001.GE8704@austin.ibm.com>
2006-09-01 3:42 ` Zhang, Yanmin
2006-09-01 9:04 ` Zhang, Yanmin
2006-09-01 21:32 ` Linas Vepstas
[not found] ` <1157081629.20092.167.camel@ymzhang-perf.sh.intel.com>
2006-09-01 21:25 ` Linas Vepstas
2006-09-04 5:47 ` Zhang, Yanmin
2006-09-04 9:03 ` Benjamin Herrenschmidt
2006-09-05 2:32 ` Zhang, Yanmin
2006-09-05 19:01 ` Linas Vepstas
2006-09-06 1:26 ` Zhang, Yanmin
2006-09-06 20:01 ` Linas Vepstas
2006-09-07 1:56 ` Zhang, Yanmin
2006-09-05 18:50 ` Linas Vepstas
2006-09-05 21:19 ` Benjamin Herrenschmidt
2006-09-06 1:35 ` Zhang, Yanmin
2006-09-05 19:17 ` Linas Vepstas
2006-09-06 2:04 ` Zhang, Yanmin
2006-09-06 20:39 ` Linas Vepstas
2006-09-07 3:18 ` Zhang, Yanmin
2006-09-12 19:38 ` Linas Vepstas [this message]
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=20060912193857.GB29167@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc-dev@ozlabs.org \
--cc=rajesh.shah@intel.com \
--cc=yanmin.zhang@intel.com \
--cc=yanmin_zhang@linux.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®