From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: Paul Mackerras <paulus@samba.org>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Greg KH <greg@kroah.com>,
ak@muc.de, linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
linux-pci@atrey.karlin.mff.cuni.cz,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: RE: PCI Error Recovery API Proposal. (WAS:: [PATCH/RFC] PCIErrorRecovery)
Date: Fri, 18 Mar 2005 09:57:58 +1100 [thread overview]
Message-ID: <1111100278.25180.21.camel@gaston> (raw)
In-Reply-To: <C7AB9DA4D0B1F344BF2489FA165E5024080FDBA3@orsmsx404.amr.corp.intel.com>
> On a fatal error the interface is down. No matter what the driver
> supports (AER aware, EEH aware, unaware) all IO is likely to fail.
> Resetting a bus in a point-to-point environment like PCI Express or EEH
> (as you describe) should have little adverse effect. The risk is the
> bus reset will cause a card reset and the driver must understand to
> re-initialize the card. A link reset in PCI Express will not cause a
> card reset. We assume the driver will reset its card if necessary.
Does the link side of PCIE provides a way to trigger a hard reset of the
rest of the card ? If not, then it's dodgy as there may be no way to
consistently "reset" the card if it's in a bad state. I have to double
check, but I suspect that IBM's implementation of EEH-compliant PCIE
will add a full hard reset not just a link reset.
next prev parent reply other threads:[~2005-03-17 22:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 18:33 PCI Error Recovery API Proposal. (WAS:: [PATCH/RFC] PCIErrorRecovery) Nguyen, Tom L
2005-03-17 22:57 ` Benjamin Herrenschmidt [this message]
2005-03-18 3:22 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2005-03-17 18:53 Nguyen, Tom L
2005-03-18 2:43 ` Benjamin Herrenschmidt
2005-03-18 4:01 ` Paul Mackerras
2005-03-18 17:17 PCI Error Recovery API Proposal. (WAS:: [PATCH/RFC]PCIErrorRecovery) Nguyen, Tom L
2005-03-18 17:24 Nguyen, Tom L
2005-03-18 18:10 ` Grant Grundler
2005-03-18 23:13 ` Benjamin Herrenschmidt
2005-03-18 18:33 Nguyen, Tom L
2005-03-18 19:29 Nguyen, Tom L
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=1111100278.25180.21.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=ak@muc.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--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