From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Ben Cheatham <Benjamin.Cheatham@amd.com>
Cc: <rafael@kernel.org>, <dan.j.williams@intel.com>,
<linux-cxl@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<yazen.ghannam@amd.com>
Subject: Re: [PATCH v6 0/5] CXL, ACPI, APEI, EINJ: Update EINJ for CXL error types
Date: Wed, 11 Oct 2023 14:40:36 +0100 [thread overview]
Message-ID: <20231011144036.00004376@Huawei.com> (raw)
In-Reply-To: <20231010200254.764273-1-Benjamin.Cheatham@amd.com>
On Tue, 10 Oct 2023 15:02:49 -0500
Ben Cheatham <Benjamin.Cheatham@amd.com> wrote:
> v6 Changes:
> - Reworked to have CXL error types under /sys/kernel/debug/cxl (Dan)
> - Removed CXL error types from legacy EINJ interface in favor of
> new interface
> - Removed cxl_rcrb_addr file
> - Added optional patch for CXL error type #defines (patch 2/5)
> - Changes to documentation updates to match rework
> - Change base to cxl-fixes branch
New approach looks good to me and I took a look at the implementation.
Couldn't find any problems to call out in the individual patches.
Feel free to add
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> The new CXL error types will use the Memory Address field in the
> SET_ERROR_TYPE_WITH_ADDRESS structure in order to target a CXL 1.1
> compliant memory-mapped downstream port. The value of the memory address
> will be in the port's MMIO range, and it will not represent physical
> (normal or persistent) memory.
>
> Add the functionality for injecting CXL 1.1 errors to the EINJ module,
> but not through the EINJ legacy interface under /sys/kernel/debug/apei/einj.
> Instead, make the error types available under /sys/kernel/debug/cxl.
> This allows for validating the MMIO address for a CXL 1.1 error type
> while also not making the user responsible for finding it.
>
> Ben Cheatham (5):
> cxl/port: Add EINJ debugfs files and callback support
> ACPI: Add CXL protocol error defines
> EINJ: Separate CXL errors from other EINJ errors
> cxl/port, EINJ: Add CXL EINJ callback functions
> EINJ: Update EINJ documentation
>
> Documentation/ABI/testing/debugfs-cxl | 27 ++++
> .../firmware-guide/acpi/apei/einj.rst | 12 ++
> drivers/acpi/apei/Kconfig | 3 +
> drivers/acpi/apei/einj.c | 149 ++++++++++++++++--
> drivers/cxl/core/port.c | 84 ++++++++++
> drivers/cxl/cxl.h | 10 ++
> include/acpi/actbl1.h | 6 +
> 7 files changed, 281 insertions(+), 10 deletions(-)
>
> base-commit: c66650d29764e228eba40b7a59fdb70fa6567daa
prev parent reply other threads:[~2023-10-11 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 20:02 [PATCH v6 0/5] CXL, ACPI, APEI, EINJ: Update EINJ for CXL error types Ben Cheatham
2023-10-10 20:02 ` [PATCH v6 1/5] cxl/port: Add EINJ debugfs files and callback support Ben Cheatham
2023-10-10 20:02 ` [PATCH v6 2/5] ACPI: Add CXL protocol error defines Ben Cheatham
2023-10-10 20:02 ` [PATCH v6 3/5] EINJ: Separate CXL errors from other EINJ errors Ben Cheatham
2023-10-10 20:02 ` [PATCH v6 4/5] cxl/port, EINJ: Add CXL EINJ callback functions Ben Cheatham
2023-10-10 22:26 ` kernel test robot
2023-10-10 20:02 ` [PATCH v6 5/5] EINJ: Update EINJ documentation Ben Cheatham
2023-10-11 13:40 ` Jonathan Cameron [this message]
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=20231011144036.00004376@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Benjamin.Cheatham@amd.com \
--cc=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=yazen.ghannam@amd.com \
/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