From: Linas Vepstas <linasvepstas@gmail.com>
To: Mike Mason <mmlnx@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Richard Lary <rlary@us.ibm.com>,
Paul Mackerras <paulus@samba.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/3] Support for PCI Express reset type
Date: Sat, 1 Aug 2009 17:43:18 -0500 [thread overview]
Message-ID: <3ae3aa420908011543t1260b971g41ee80fa78c4f471@mail.gmail.com> (raw)
In-Reply-To: <4A721FB1.4040903@us.ibm.com>
2009/7/30 Mike Mason <mmlnx@us.ibm.com>:
> This is the first of three patches that implement a bit field that PCI
> Express device drivers can use to indicate they need a fundamental reset
> during error recovery.
>
> By default, the EEH framework on powerpc does what's known as a "hot rese=
t"
> during recovery of a PCI Express device. =C2=A0We've found a case where t=
he
> device needs a "fundamental reset" to recover properly. =C2=A0The current=
PCI
> error recovery and EEH frameworks do not support this distinction.
>
> The attached patch (courtesy of Richard Lary) adds a bit field to pci_dev
> that indicates whether the device requires a fundamental reset during
> recovery.
>
> These patches supersede the previously submitted patch that implemented a
> fundamental reset bit field.
> Please review and let me know of any concerns.
>
> Signed-off-by: Mike Mason <mmlnx@us.ibm.com>
> Signed-off-by: Richard Lary <rlary@us.ibm.com>
Signed-off-by: Linas Vepstas <linasvepstas@gmail.com>
next prev parent reply other threads:[~2009-08-01 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 22:33 [PATCH 1/3] Support for PCI Express reset type Mike Mason
2009-07-31 16:19 ` Andi Kleen
2009-07-31 16:47 ` Andrew Vasquez
2009-08-01 22:40 ` Linas Vepstas
2009-08-01 22:43 ` Linas Vepstas [this message]
2009-08-14 16:54 ` Jesse Barnes
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=3ae3aa420908011543t1260b971g41ee80fa78c4f471@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mmlnx@us.ibm.com \
--cc=paulus@samba.org \
--cc=rlary@us.ibm.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;
as well as URLs for NNTP newsgroup(s).