From: Pierre Gondois <pierre.gondois@arm.com>
To: Mark Brown <broonie@debian.org>
Cc: linux-kernel@vger.kernel.org, James Morse <james.morse@arm.com>,
Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Tony Luck <tony.luck@intel.com>,
Borislav Petkov <bp@alien8.de>, Hanjun Guo <guohanjun@huawei.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shuai Xue <xueshuai@linux.alibaba.com>,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
Pawel Chmielewski <pawel.chmielewski@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
"Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>,
Breno Leitao <leitao@debian.org>, Dan Williams <djbw@kernel.org>,
Terry Bowman <terry.bowman@amd.com>,
Ard Biesheuvel <ardb@kernel.org>,
Morduan Zang <zhangdandan@uniontech.com>,
linux-acpi@vger.kernel.org, linux-edac@vger.kernel.org,
acpica-devel@lists.linux.dev
Subject: Re: [PATCH v3 6/7] ACPI: APEI: add separate Memory Error Section 2 handlers
Date: Mon, 9 Nov 2026 11:55:22 +0100 [thread overview]
Message-ID: <4eea61c1-01d2-4481-9339-c09d8ee9547a@arm.com> (raw)
In-Reply-To: <94b213b2-dabc-46b4-8d21-a5dc8e8e51bb@sirena.org.uk>
On 11/4/26 18:51, Mark Brown wrote:
> On Wed, Nov 04, 2026 at 12:03:14PM +0100, Pierre Gondois wrote:
>> Add dedicated GHES and EDAC callbacks for Memory Error Section 2
>> records. Use a separate GHES notifier chain so existing consumers
>> continue to receive legacy memory error sections.
>> @@ -1008,6 +1021,16 @@ static void ghes_do_proc(struct ghes *ghes,
>>
>> arch_apei_report_mem_error(sev, mem_err);
>> queued |= ghes_handle_memory_failure(gdata, sev, sync);
>> + } else if (guid_equal(sec_type, &CPER_SEC_PLATFORM_MEM2)) {
>> + struct cper_sec_mem_err2 *mem_err = acpi_hest_get_payload(gdata);
>> +
>> + if (gdata->error_data_length < sizeof(*mem_err)) {
>> + pr_warn(FW_WARN "Memory Error Section 2 length is too small\n");
> The v1 code uses pr_warn_ratelimited() which seems sensible.
yes right
>
>> +static int ghes_edac_report_mem_error2(struct notifier_block *nb,
>> + unsigned long val, void *data)
>> +{
>> + struct cper_sec_mem_err2 *mem_err = data;
>> + struct edac_raw_error_desc *e;
>> + struct mem_ctl_info *mci;
>> + struct ghes_pvt *pvt;
>> + char *p;
>> + /* Memory error location, mapped on e->location */
>> + p = e->location;
>> + p += cper_mem_err2_location(mem_err, p);
>> +
>> + if (mem_err->validation_bits & CPER_MEM2_VALID_MODULE_HANDLE) {
>> + struct dimm_info *dimm = NULL;
>> +
>> + p += cper_dimm_err2_location(mem_err, p);
> Do we need to raise the size of e->location? It's 256 bytes and
> there's an awful ot of potential fields that could be decoded here,
> including some with 64 bit IDs.
cper_mem_err2_location()
node:0000 card:0000 module:0000 rank:0000 bank:0000 bank_group:0000
bank_address:0000 device:0000 row:0000 column:0000 bit_position:0000
requestor_id:0x0000000000000000 responder_id:0x0000000000000000
target_id:0x0000000000000000 chip_id:0000
~244 chars
cper_dimm_err2_location()
DIMM location: not present. DMI handle: 0x00000000
~51 chars
DIMM location: %s %s
~depends on string length
So indeed LOCATION_SIZE should be increased,
512 chars should be better.
>> + if (mem_err->mem_dev_handle <= U16_MAX)
>> + dimm = find_dimm_by_handle(mci, mem_err->mem_dev_handle);
>> + else
>> + pr_warn(FW_WARN "Memory Error Section 2 module handle 0x%x exceeds SMBIOS range\n",
>> + mem_err->mem_dev_handle);
> There's an equivalent print in cper_dimm_err2_location().
Right, I ll remove this one
next prev parent reply other threads:[~2026-11-09 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 11:03 [PATCH v3 0/7] CPER: Add Memory Error Section 2 support Pierre Gondois
2026-11-04 11:03 ` [PATCH v3 1/7] cper: use BIT_ULL() for processor and memory validation bits Pierre Gondois
2026-11-04 16:22 ` Mark Brown
2026-11-04 11:03 ` [PATCH v3 2/7] cper: add Memory Error Section 2 structures Pierre Gondois
2026-11-04 11:03 ` [PATCH v3 3/7] cper: add helpers to handle Memory Error Section 2 Pierre Gondois
2026-11-04 17:25 ` Mark Brown
2026-11-09 10:56 ` Pierre Gondois
2026-11-04 11:03 ` [PATCH v3 4/7] EDAC/ghes: Extract error report initialization Pierre Gondois
2026-11-04 11:03 ` [PATCH v3 5/7] ACPI: APEI: Extract common memory failure handling Pierre Gondois
2026-11-04 11:03 ` [PATCH v3 6/7] ACPI: APEI: add separate Memory Error Section 2 handlers Pierre Gondois
2026-11-04 17:51 ` Mark Brown
2026-11-09 10:55 ` Pierre Gondois [this message]
2026-11-04 11:03 ` [PATCH v3 7/7] ACPI: extlog: add Memory Error Section 2 trace event Pierre Gondois
2026-11-04 11:07 ` [PATCH v3 0/7] CPER: Add Memory Error Section 2 support Pierre Gondois
2026-11-09 10:57 ` Pierre Gondois
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=4eea61c1-01d2-4481-9339-c09d8ee9547a@arm.com \
--to=pierre.gondois@arm.com \
--cc=acpica-devel@lists.linux.dev \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=broonie@debian.org \
--cc=dave.jiang@intel.com \
--cc=djbw@kernel.org \
--cc=fabio.m.de.francesco@linux.intel.com \
--cc=guohanjun@huawei.com \
--cc=james.morse@arm.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=leitao@debian.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=mchehab@kernel.org \
--cc=pawel.chmielewski@intel.com \
--cc=rafael@kernel.org \
--cc=terry.bowman@amd.com \
--cc=tony.luck@intel.com \
--cc=xueshuai@linux.alibaba.com \
--cc=zhangdandan@uniontech.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
all inboxes | Powered by JetHome®