From: Andi Kleen <ak@muc.de>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PCI Error reporting & recovery
Date: Tue, 08 Feb 2005 12:55:41 +0100 [thread overview]
Message-ID: <m1is531d1e.fsf@muc.de> (raw)
In-Reply-To: <420876DC.3040201@jp.fujitsu.com> (Hidetoshi Seto's message of "Tue, 08 Feb 2005 17:22:52 +0900")
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> writes:
>
> It goes slowly but steadily...
> I'd also like to start the discussion about PCI error reporting again.
It's much more interesting now than it used to be because PCI-Express
is now mainstream and it has standard registers to report errors.
Whatever is adopted should definitely try to handle this.
Unfortunately no standardized exceptions, but at least some Opteron
chipsets can raise NMIs in this case when programmed right.
-Andi
next prev parent reply other threads:[~2005-02-08 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 4:11 PCI Error reporting & recovery Benjamin Herrenschmidt
2005-02-08 8:22 ` Hidetoshi Seto
2005-02-08 11:55 ` Andi Kleen [this message]
2005-02-10 0:59 ` Benjamin Herrenschmidt
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=m1is531d1e.fsf@muc.de \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=seto.hidetoshi@jp.fujitsu.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