* PCI error recovery patch [was: Request for feedback]
[not found] <CAHrUA35gL7=PjjqsgH3T=MRnM7LuzKAT1g8+DkZLMfGvJOy3KQ@mail.gmail.com>
@ 2012-11-08 19:12 ` Linas Vepstas
0 siblings, 0 replies; 2+ messages in thread
From: Linas Vepstas @ 2012-11-08 19:12 UTC (permalink / raw)
To: linux-pci; +Cc: Pandarathil, Vijaymohan R
Hi Vijay,
I no longer actively maintain the error recovery stack. However, your patch
and explanation for it looks reasonable to me --- it was certainly never the
intent that a non-capable driver report a successful recovery.
I'm guessing that the bug that you are fixing was introduced when the
original pci error recovery code was integrated with AER (PCI-AER was
standardized after the original error recovery system was created, and I did
not really pay very much attention to AER at the time).
FWIW, I guess I could add a
Signed-off-by: Linas Vepstas <linasvepstas@gmail.com>
but I'm not sure that really means much any more :-)
-- Linas
On 7 November 2012 21:50, Pandarathil, Vijaymohan R
<vijaymohan.pandarathil@hp.com> wrote:
> Hi Bjorn/Linas,
>
> I got your names from the PCI/PCI-error-recovery maintainers list. I had
> posted the following request last week.
> http://article.gmane.org/gmane.linux.kernel.pci/18465
>
> Being a newbie, it would be extremely helpful to get your guidance on
> these changes, specifically on any side effects it has. I am also working
> on another set of patches to improve the PCI error recovery/containment
> capabilities of KVM. But if the above change cannot be made first, I may
> have to figure out alternate approach for the second set of patches.
>
> Thanks
>
> Vijay
^ permalink raw reply [flat|nested] 2+ messages in thread
* PCI error recovery patch [was: Request for feedback]
@ 2012-11-08 19:14 Linas Vepstas
0 siblings, 0 replies; 2+ messages in thread
From: Linas Vepstas @ 2012-11-08 19:14 UTC (permalink / raw)
To: linux-pci; +Cc: Pandarathil, Vijaymohan R
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
Hi Vijay,
I no longer actively maintain the error recovery stack. However, your patch
and explanation for it looks reasonable to me --- it was certainly never the
intent that a non-capable driver report a successful recovery.
I'm guessing that the bug that you are fixing was introduced when the
original pci error recovery code was integrated with AER (PCI-AER was
standardized after the original error recovery system was created, and I did
not really pay very much attention to AER at the time).
FWIW, I guess I could add a
Signed-off-by: Linas Vepstas <linasvepstas@gmail.com>
but I'm not sure that really means much any more :-)
-- Linas
On 7 November 2012 21:50, Pandarathil, Vijaymohan R <vijaymohan.pandarathil@hp.com> wrote:
> Hi Bjorn/Linas,
>
> I got your names from the PCI/PCI-error-recovery maintainers list. I had
> posted the following request last week.
> http://article.gmane.org/gmane.linux.kernel.pci/18465
>
> Being a newbie, it would be extremely helpful to get your guidance on
> these changes, specifically on any side effects it has. I am also working
> on another set of patches to improve the PCI error recovery/containment
> capabilities of KVM. But if the above change cannot be made first, I may
> have to figure out alternate approach for the second set of patches.
>
> Thanks
>
> Vijay
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-11-08 19:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-08 19:14 PCI error recovery patch [was: Request for feedback] Linas Vepstas
[not found] <CAHrUA35gL7=PjjqsgH3T=MRnM7LuzKAT1g8+DkZLMfGvJOy3KQ@mail.gmail.com>
2012-11-08 19:12 ` Linas Vepstas
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.