[lkml]   [2018]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v13 0/6] Address error and recovery for AER and DPC
On 2018-04-16 09:23, Sinan Kaya wrote:
> On 4/15/2018 11:16 PM, Bjorn Helgaas wrote:
>> On Mon, Apr 09, 2018 at 10:41:48AM -0400, Oza Pawandeep wrote:
>>> This patch set brings in error handling support for DPC
>>> The current implementation of AER and error message broadcasting to
>>> the
>>> EP driver is tightly coupled and limited to AER service driver.
>>> It is important to factor out broadcasting and other link handling
>>> callbacks. So that not only when AER gets triggered, but also when
>>> DPC get
>>> triggered (for e.g. ERR_FATAL), callbacks are handled appropriately.
>>> DPC should behave identical to AER as far as error handling is
>>> concerned.
>>> DPC should remove the devices and not to do recovery for hotplug
>>> enabled system.
>> Is there a specific bug that's fixed by these patches? I didn't see
>> one mentioned in the changelogs.
> There is no actual bug.
> We realized that DPC and hotplug is heavily integrated today. We have
> use
> cases for systems without hotplug support but still support DPC. That's
> the
> problem we are trying to solve with this patchset.

Adding to what Sinan said;

DPC should handle the error handling and recovery similar to AER,
because finally both
are attempting recovery in some or the other way,
and for that error handling and recovery framework has to be loosely
It achieves uniformity and transparency to the error handling agents
such as AER, DPC, with respect to recovery and error handling.

So, this patch-set tries to unify lot of things between error agents and
make them behave in a well defined way. (be it error (FATAL, NON_FATAL)
handling or recovery).


 \ /
  Last update: 2018-04-16 08:03    [W:0.049 / U:35.140 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site