From: Zaid Alali <zaidal@os.amperecomputing.com>
To: rafael@kernel.org, lenb@kernel.org, james.morse@arm.com,
tony.luck@intel.com, bp@alien8.de, kees@kernel.org,
gustavoars@kernel.org, zaidal@os.amperecomputing.com,
Jonathan.Cameron@huawei.com, sudeep.holla@arm.com,
u.kleine-koenig@baylibre.com, jonathanh@nvidia.com,
viro@zeniv.linux.org.uk, ira.weiny@intel.com,
peterz@infradead.org, sthanneeru.opensrc@micron.com,
gregkh@linuxfoundation.org, Benjamin.Cheatham@amd.com,
dave.jiang@intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: [PATCH v8 0/7] Enable EINJv2 Support
Date: Wed, 4 Jun 2025 15:37:57 -0700 [thread overview]
Message-ID: <20250604223804.842501-1-zaidal@os.amperecomputing.com> (raw)
The goal of this update is to allow the driver to simultaneously
support EINJ and EINJv2. The implementation follows ACPI 6.6
specs[1] that enables the driver to discover system capabilities
through GET_ERROR_TYPE.
Link: https://uefi.org/specs/ACPI/6.6/18_Platform_Error_Interfaces.html#error-injection [1]
V5:
*Users no longer input component array size, instead it
is counted by parsing the component array itself.
V6:
*Fix memory leak.
*If EINJv2 initialization failed, EINJv1 will still work, and
probe function will continue with disabled EINJv2.
V7:
*Update component array to take 128-bit values to match ACPI specs.
*Enable Vendor EINJv2 injections
*Moved component array parsing and validating to a separate
function to improve readability.
V8:
*Update UI to use single value files for component array.
*Update links to point to recent ACPI 6.6 spec release.
*Updated commit messages and documentation patch.
*Dropped the first two patches as they were merged via
ACPICA project.
Tony Luck (1):
ACPI: APEI: EINJ: Create debugfs files to enter device id and syndrome
Zaid Alali (6):
ACPI: APEI: EINJ: Fix kernel test sparse warnings
ACPI: APEI: EINJ: Enable the discovery of EINJv2 capabilities
ACPI: APEI: EINJ: Add einjv2 extension struct
ACPI: APEI: EINJ: Discover EINJv2 parameters
ACPI: APEI: EINJ: Enable EINJv2 error injections
ACPI: APEI: EINJ: Update the documentation for EINJv2 support
.../firmware-guide/acpi/apei/einj.rst | 33 ++
drivers/acpi/apei/apei-internal.h | 2 +-
drivers/acpi/apei/einj-core.c | 371 ++++++++++++++----
drivers/acpi/apei/einj-cxl.c | 2 +-
4 files changed, 339 insertions(+), 69 deletions(-)
--
2.43.0
next reply other threads:[~2025-06-04 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 22:37 Zaid Alali [this message]
2025-06-04 22:37 ` [PATCH v8 1/7] ACPI: APEI: EINJ: Fix kernel test sparse warnings Zaid Alali
2025-06-04 22:37 ` [PATCH v8 2/7] ACPI: APEI: EINJ: Enable the discovery of EINJv2 capabilities Zaid Alali
2025-06-04 22:38 ` [PATCH v8 3/7] ACPI: APEI: EINJ: Add einjv2 extension struct Zaid Alali
2025-06-04 22:38 ` [PATCH v8 4/7] ACPI: APEI: EINJ: Discover EINJv2 parameters Zaid Alali
2025-06-04 22:38 ` [PATCH v8 5/7] ACPI: APEI: EINJ: Create debugfs files to enter device id and syndrome Zaid Alali
2025-06-04 22:38 ` [PATCH v8 6/7] ACPI: APEI: EINJ: Enable EINJv2 error injections Zaid Alali
2025-06-04 22:38 ` [PATCH v8 7/7] ACPI: APEI: EINJ: Update the documentation for EINJv2 support Zaid Alali
2025-06-04 23:44 ` [PATCH v8 0/7] Enable EINJv2 Support Luck, Tony
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=20250604223804.842501-1-zaidal@os.amperecomputing.com \
--to=zaidal@os.amperecomputing.com \
--cc=Benjamin.Cheatham@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bp@alien8.de \
--cc=dave.jiang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=ira.weiny@intel.com \
--cc=james.morse@arm.com \
--cc=jonathanh@nvidia.com \
--cc=kees@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=sthanneeru.opensrc@micron.com \
--cc=sudeep.holla@arm.com \
--cc=tony.luck@intel.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=viro@zeniv.linux.org.uk \
/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