On Fri, 2018-05-04 at 12:55 +1000, Michael Ellerman wrote: > Sam Bobroff <sbobr...@linux.ibm.com> writes: > > > Add a single log line at the end of successful EEH recovery, so > > that > > it's clear that event processing has finished. > > > > Signed-off-by: Sam Bobroff <sbobr...@linux.ibm.com> > > --- > > arch/powerpc/kernel/eeh_driver.c | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/arch/powerpc/kernel/eeh_driver.c > > b/arch/powerpc/kernel/eeh_driver.c > > index 56a60b9eb397..07e0a42035ce 100644 > > --- a/arch/powerpc/kernel/eeh_driver.c > > +++ b/arch/powerpc/kernel/eeh_driver.c > > @@ -910,6 +910,7 @@ void eeh_handle_normal_event(struct eeh_pe *pe) > > pr_info("EEH: Notify device driver to resume\n"); > > eeh_pe_dev_traverse(pe, eeh_report_resume, NULL); > > > > + pr_info("EEH: Recovery successful.\n"); > Is it possible for recovery for multiple devices to be interleaved? > > Should that message include the device?
Pretty sure EEH will only process a single error at a time so this *should* always let you infer from context, but PHB and PE should probably be included anyway. It'd be cool to move pe_{err/warn/info}() out of powernv for messages like this. - Russell > > cheers