From: Prarit Bhargava <prarit@redhat.com>
To: Shyam_Iyer@Dell.com
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com
Subject: Re: [PATCH] pci, Add AER_panic sysfs file
Date: Thu, 17 May 2012 13:39:00 -0400 [thread overview]
Message-ID: <4FB537B4.1040505@redhat.com> (raw)
In-Reply-To: <DBFB1B45AF80394ABD1C807E9F28D15707BC8F0CE9@BLRX7MCDC203.AMER.DELL.COM>
On 05/17/2012 01:29 PM, Shyam_Iyer@Dell.com wrote:
>
>
>> -----Original Message-----
>> From: linux-pci-owner@vger.kernel.org [mailto:linux-pci-
>> owner@vger.kernel.org] On Behalf Of Prarit Bhargava
>> Sent: Thursday, May 17, 2012 1:05 PM
>> To: linux-pci@vger.kernel.org
>> Cc: Prarit Bhargava; Bjorn Helgaas
>> Subject: [PATCH] pci, Add AER_panic sysfs file
>>
>> Consider the following case
>>
>> [ RP ]
>> |
>> |
>> +---------+-----------+
>> | | |
>> [H1] [H2] [X1]
>>
>> where RP is a PCIE Root Port, H1 and H2 are devices with drivers that
>> support
>> PCIE AER driver error handling (ie, they have pci_error_handlers
>> defined in
>> the driver), and X1 is a device with a driver that does not support
>> PCIE
>> AER driver error handling.
>>
>> If the Root Port takes an error what currently happens is that the
>> bus resets and H1 & H2 call their slot_reset functions. X1 does
>> nothing.
>>
>> In some cases a user may not wish the system to continue because X1 is
>> an unhardened driver. In these cases, the system should not do a bus
>> reset,
>> but rather the system should panic to avoid any further possible data
>> corruption.
>
> Do we neeed to panic for both correctable and uncorrectable errors.. ?
>
> I thought correctable errors could recover without a bus reset.
Will a bus reset be issued on a correctable error? I thought the code path was
that the bus reset was issued on the uncorrectable error.
drivers/pci/pcie/aer/aerdrv_core.c: do_recovery()
if (severity == AER_FATAL) {
result = reset_link(dev);
if (result != PCI_ERS_RESULT_RECOVERED)
goto failed;
}
I may not be looking at the right spot of code. Care to enlighten me? :)
P.
next prev parent reply other threads:[~2012-05-17 17:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 17:04 [PATCH] pci, Add AER_panic sysfs file Prarit Bhargava
2012-05-17 17:29 ` Shyam_Iyer
2012-05-17 17:39 ` Prarit Bhargava [this message]
2012-05-17 17:51 ` Shyam_Iyer
[not found] ` <DBFB1B45AF80394ABD1C807E9F28D15707BC712175@BLRX7MCDC203.AMER.DELL.COM>
2012-05-17 18:00 ` Shyam_Iyer
2012-05-17 18:51 ` Don Dutile
2012-05-17 18:54 ` Prarit Bhargava
2012-05-17 19:11 ` Don Dutile
2012-05-17 22:16 ` Prarit Bhargava
2012-05-17 21:32 ` Betty Dall
2012-05-18 4:51 ` Greg KH
2012-05-18 10:26 ` Prarit Bhargava
2012-05-18 14:16 ` Prarit Bhargava
2012-05-18 15:47 ` Greg KH
2012-05-18 17:17 ` Prarit Bhargava
2012-05-18 18:13 ` Greg KH
2012-05-18 19:28 ` Prarit Bhargava
2012-05-18 23:19 ` Greg KH
2012-05-18 17:26 ` Prarit Bhargava
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=4FB537B4.1040505@redhat.com \
--to=prarit@redhat.com \
--cc=Shyam_Iyer@Dell.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
/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).