From: Marc Herbert <marc.herbert@linux.intel.com>
To: "Koralahalli Channabasappa,
Smita" <Smita.KoralahalliChannabasappa@amd.com>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-cxl@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Terry Bowman <terry.bowman@amd.com>,
Dave Jiang <dave.jiang@intel.com>,
tony.luck@intel.com, Gregory Price <gourry@gourry.net>
Subject: Re: "invalid agent type: 1" in acpi/ghes, cper: Recognize and cache CXL Protocol errors
Date: Mon, 28 Jul 2025 22:41:54 -0700 [thread overview]
Message-ID: <ef9c9418-2def-484a-89fb-b0235391ad83@linux.intel.com> (raw)
In-Reply-To: <dfc6cedd-c125-4201-a98b-cbaa84a4f370@amd.com>
On 2025-07-28 09:25, Koralahalli Channabasappa, Smita wrote:
> On 7/22/2025 12:24 PM, Marc Herbert wrote:
>> The code below triggers the error "invalid agent type: 1" in Intel
>> validation (internal issue 15018133056)
>>
>> It's not clear to anyone we asked why you did not include RCH_DP in
>> the `switch (prot_err->agent_type)` in cxl_cper_post_prot_err() below.
>>
>> I can see how RCH_DP is special in cxl_cper_PRINT_prot_err() and I can
>> even understand (despite my near-zero CPER knowledge) some of the
>> special cases there. But in cxl_cper_post_prot_err() here, it's not
>> clear why RCH_DP would be rejected. Could this be an oversight? If not,
>> a comment with a short explanation would not hurt.
>>
>
> You're right. RCH_DP was excluded because it doesn’t report a valid
> SBDF in the CPER record. Instead, it provides only the RCRB base
> address.
>
> I haven't thoroughly investigated whether SBDF can be reliably derived
> from the RCRB base. There might be a platform-specific mechanism for
> that, but at the time, it seemed non-trivial to implement. Introducing
> additional infrastructure solely to support RCH_DP felt like it was
> adding more complexity.
>
> I agree that a brief comment explaining this rationale would help. I'm
> okay if you plan to include a fixup for this along with the one for
> the device serial number.
If I understood you correctly, I think a different error message
would be much better than a comment. Like this?
--- a/drivers/acpi/apei/ghes.c
+++ b/drivers/acpi/apei/ghes.c
@@ -730,6 +730,9 @@ static void cxl_cper_post_prot_err(struct cxl_cper_sec_prot_err *prot_err,
memcpy(&wd.ras_cap, cap_start, sizeof(wd.ras_cap));
wd.severity = cper_severity_to_aer(severity);
break;
+ case RCH_DP:
+ pr_err_ratelimited("CXL CPER agent type unsupported: RCH_DP\n");
+ return;
default:
pr_err_ratelimited("CXL CPER invalid agent type: %d\n",
prot_err->agent_type);
next prev parent reply other threads:[~2025-07-29 5:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 8:44 [PATCH v6 0/6] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors Smita Koralahalli
2025-01-23 8:44 ` [PATCH v6 1/6] efi/cper, cxl: Prefix protocol error struct and function names with cxl_ Smita Koralahalli
2025-02-04 0:12 ` Fan Ni
2025-02-05 19:17 ` Gregory Price
2025-01-23 8:44 ` [PATCH v6 2/6] efi/cper, cxl: Make definitions and structures global Smita Koralahalli
2025-02-04 0:16 ` Fan Ni
2025-02-05 19:16 ` Gregory Price
2025-02-06 10:54 ` Jonathan Cameron
2025-02-06 16:14 ` Gregory Price
2025-02-06 17:14 ` Konstantin Ryabitsev
2025-02-06 17:32 ` Gregory Price
2025-01-23 8:44 ` [PATCH v6 3/6] efi/cper, cxl: Remove cper_cxl.h Smita Koralahalli
2025-02-04 0:20 ` Fan Ni
2025-02-05 19:18 ` Gregory Price
2025-01-23 8:44 ` [PATCH v6 4/6] acpi/ghes, cper: Recognize and cache CXL Protocol errors Smita Koralahalli
2025-02-03 18:59 ` Luck, Tony
2025-02-05 19:35 ` Gregory Price
2025-02-05 22:21 ` Dan Williams
2025-07-22 19:24 ` "invalid agent type: 1" in " Marc Herbert
2025-07-23 7:13 ` Marc Herbert
2025-07-24 14:49 ` Fabio M. De Francesco
2025-07-25 11:04 ` Jonathan Cameron
2025-07-28 15:01 ` dan.j.williams
2025-07-28 16:25 ` Koralahalli Channabasappa, Smita
2025-07-29 5:41 ` Marc Herbert [this message]
2025-07-29 15:52 ` Koralahalli Channabasappa, Smita
2025-07-29 17:39 ` dan.j.williams
2025-01-23 8:44 ` [PATCH v6 5/6] acpi/ghes, cxl/pci: Process CXL CPER Protocol Errors Smita Koralahalli
2025-02-03 19:03 ` Luck, Tony
2025-02-12 21:04 ` Koralahalli Channabasappa, Smita
2025-02-05 19:50 ` Gregory Price
2025-02-05 22:58 ` Dan Williams
2025-02-12 20:57 ` Koralahalli Channabasappa, Smita
2025-01-23 8:44 ` [PATCH v6 6/6] cxl/pci: Add trace logging for CXL PCIe Port RAS errors Smita Koralahalli
2025-01-24 16:36 ` Ira Weiny
2025-02-05 20:01 ` Gregory Price
2025-02-05 23:06 ` Dan Williams
2025-02-03 17:09 ` [PATCH v6 0/6] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors Dave Jiang
2025-02-06 18:38 ` Dave Jiang
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=ef9c9418-2def-484a-89fb-b0235391ad83@linux.intel.com \
--to=marc.herbert@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=alison.schofield@intel.com \
--cc=ardb@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terry.bowman@amd.com \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@intel.com \
--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 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.