From: Eddie James <eajames@linux.ibm.com>
To: linux-fsi@lists.ozlabs.org
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
joel@jms.id.au, linux@roeck-us.net, jdelvare@suse.com,
alistair@popple.id.au, jk@ozlabs.org, eajames@linux.ibm.com
Subject: [PATCH 0/3] occ: fsi and hwmon: Extract and provide the SBEFIFO FFDC
Date: Tue, 14 Sep 2021 16:35:40 -0500 [thread overview]
Message-ID: <20210914213543.73351-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.
Eddie James (3):
fsi: occ: Use a large buffer for responses
fsi: occ: Store the SBEFIFO FFDC in the user response buffer
hwmon: (occ) Provide the SBEFIFO FFDC in binary sysfs
drivers/fsi/fsi-occ.c | 184 ++++++++++++++++++++-----------------
drivers/hwmon/occ/p9_sbe.c | 98 +++++++++++++++++++-
include/linux/fsi-occ.h | 3 +
3 files changed, 202 insertions(+), 83 deletions(-)
--
2.27.0
next reply other threads:[~2021-09-14 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 21:35 Eddie James [this message]
2021-09-14 21:35 ` [PATCH 1/3] fsi: occ: Use a large buffer for responses Eddie James
2021-09-14 21:35 ` [PATCH 2/3] fsi: occ: Store the SBEFIFO FFDC in the user response buffer Eddie James
2021-09-14 21:35 ` [PATCH 3/3] hwmon: (occ) Provide the SBEFIFO FFDC in binary sysfs Eddie James
2021-09-15 16:13 ` Guenter Roeck
2021-09-15 21:11 ` Eddie James
2021-09-16 7:27 ` Joel Stanley
2021-09-16 0:17 ` Jeremy Kerr
2021-09-17 18:44 ` Eddie James
2021-09-21 15:37 ` Greg KH
2021-09-21 15:57 ` Eddie James
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=20210914213543.73351-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.