From: Eddie James <eajames@linux.ibm.com>
To: linux-fsi@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
jk@ozlabs.org, joel@jms.id.au, alistair@popple.id.au,
linux@roeck-us.net, jdelvare@suse.com,
Eddie James <eajames@linux.ibm.com>
Subject: [PATCH v3 0/4] occ: fsi and hwmon: Extract and provide the SBEFIFO FFDC
Date: Mon, 27 Sep 2021 10:59:21 -0500 [thread overview]
Message-ID: <20210927155925.15485-1-eajames@linux.ibm.com> (raw)
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
next reply other threads:[~2021-09-27 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 15:59 Eddie James [this message]
2021-09-27 15:59 ` [PATCH v3 1/4] fsi: occ: Use a large buffer for responses Eddie James
2021-10-15 5:05 ` Joel Stanley
2021-10-19 20:22 ` Eddie James
2021-09-27 15:59 ` [PATCH v3 2/4] fsi: occ: Store the SBEFIFO FFDC in the user response buffer Eddie James
2021-10-15 5:05 ` Joel Stanley
2021-10-19 20:16 ` Eddie James
2021-09-27 15:59 ` [PATCH v3 3/4] docs: ABI: testing: Document the OCC hwmon FFDC binary interface Eddie James
2021-09-27 15:59 ` [PATCH v3 4/4] hwmon: (occ) Provide the SBEFIFO FFDC in binary sysfs Eddie James
2021-10-11 14:38 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210927155925.15485-1-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=alistair@popple.id.au \
--cc=jdelvare@suse.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox