[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210927155925.15485-1-eajames@linux.ibm.com>
Date: Mon, 27 Sep 2021 10:59:21 -0500
From: Eddie James <eajames@...ux.ibm.com>
To: linux-fsi@...ts.ozlabs.org
Cc: linux-kernel@...r.kernel.org, linux-hwmon@...r.kernel.org,
jk@...abs.org, joel@....id.au, alistair@...ple.id.au,
linux@...ck-us.net, jdelvare@...e.com,
Eddie James <eajames@...ux.ibm.com>
Subject: [PATCH v3 0/4] occ: fsi and hwmon: Extract and provide the SBEFIFO FFDC
Currently, users have no way to obtain the FFDC (First Failure Data
Capture) provided by the SBEFIFO when an operation fails. To remedy this,
add code in the FSI OCC driver to store this FFDC in the user's response
buffer and set the response length accordingly.
On the hwmon side, there is a need at the application level to perform
side-band operations in response to SBE errors. Therefore, add a new
binary sysfs file that provides the FFDC (or lack thereof) when there is
an SBEFIFO error. Now applications can take action when an SBE error is
detected.
Changes since v2:
- Add documentation
Changes since v1:
- Remove the magic value that indicated an SBE/SBEFIFO error with no
FFDC.
- Remove binary sysfs state management and intead just clear the error
flag when the whole FFDC has been read.
Eddie James (4):
fsi: occ: Use a large buffer for responses
fsi: occ: Store the SBEFIFO FFDC in the user response buffer
docs: ABI: testing: Document the OCC hwmon FFDC binary interface
hwmon: (occ) Provide the SBEFIFO FFDC in binary sysfs
.../sysfs-bus-platform-devices-occ-hwmon | 13 ++
drivers/fsi/fsi-occ.c | 163 +++++++++---------
drivers/hwmon/occ/p9_sbe.c | 86 ++++++++-
include/linux/fsi-occ.h | 2 +
4 files changed, 184 insertions(+), 80 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-platform-devices-occ-hwmon
--
2.27.0
Powered by blists - more mailing lists