mbox series

[0/3] xscom: Don't create PELs for non-severe read/write failures

Message ID 1575465990-25353-1-git-send-email-ego@linux.vnet.ibm.com
Headers show
Series xscom: Don't create PELs for non-severe read/write failures | expand

Message

Gautham R Shenoy Dec. 4, 2019, 1:26 p.m. UTC 
From: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>

Under certain conditions, xscom read/write calls initiated by the
userspace (either via HBRT or xscom-utils) can fail with an "invalid
address" status due to known hardware errors. These failures are not
severe and can be handled by the callers. Thus we need not create
elogs for them.

This patchset ensures that when xscom read/write calls initiated via
respective OPAL calls fail with a "invalid address" status, we only
log the error in the OPAL msglog and do not create PEL records such
errors. Note that we continue to create PEL records for all other
xscom read/write failures.

Gautham R. Shenoy (3):
  xscom: Conditionally create elogs for read/write addr failures
  xscom: Add a create_addr_elog parameter to _xscom_read/write() calls
  xscom: Don't create PEL for non-severe xscom_read/write opal-call fail

 hw/sbe-p8.c     |  7 +++---
 hw/xscom.c      | 66 ++++++++++++++++++++++++++++++++++++++++++++++-----------
 include/xscom.h | 10 +++++----
 3 files changed, 64 insertions(+), 19 deletions(-)