From: Pierre Gondois <pierre.gondois@arm.com>
To: Ashok Raj <ashok.raj@oss.qualcomm.com>
Cc: linux-kernel@vger.kernel.org, James Morse <james.morse@arm.com>,
Mark Brown <broonie@kernel.org>,
"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>,
Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>,
"Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>,
Breno Leitao <leitao@debian.org>,
Terry Bowman <terry.bowman@amd.com>,
Dan Williams <djbw@kernel.org>, 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 0/7] CPER: Add Memory Error Section 2 support
Date: Mon, 9 Nov 2026 11:57:43 +0100 [thread overview]
Message-ID: <62430a5e-1e43-45de-9f8b-f0fdc826f38b@arm.com> (raw)
In-Reply-To: <7c59eada-ea8d-4b04-a24b-9ba6aa2a6c64@arm.com>
Gentle ping to check if there are additional comments on this version.
(Thanks Mark for the review)
On 11/4/26 12:07, Pierre Gondois wrote:
> + Ashok
>
> On 11/4/26 12:03, Pierre Gondois wrote:
>> The support is mostly duplicated from Memory Error Section handling.
>> Other than differences coming from the content of Memory Error
>> Section 1 and 2, differences in the support are:
>>
>> - v2 do not rely on a compact "struct cper_mem_err_compact" struct.
>> This structure was used to support older versions of the Memory
>> Error Section (1). This is not needed for the new structure.
>>
>> - The compact version is also used by the tracing framework.
>> To avoid relying and propagating a non-standard record format,
>> through trace event (cf. extlog_mem event) the new trace event
>> prints each field individually.
>>
>> The last patch of the serie was only build-tested due to the
>> absence of relevant hardware. apei_mce_report_mem_error() and
>> arch_apei_report_mem_error() implementations were also removed since
>> last version.
>>
>> It will also require a proper handling from the rasdaemon. Applying
>> this last patch without rasdaemon support will silent the reports of
>> Memory Error Section 2 error, cf. ras_userspace_consumers() check.
>>
>> Future:
>> - _OSC support
>> - Addition of arm64 tracepoints
>> https://lore.kernel.org/lkml/20261023170405.000060b8@oss.qualcomm.com/
>> - Emission of lossy CPER Mem error v1 tracepoints for legacy userspace
>> tools
>> https://lore.kernel.org/lkml/at0rs4parlHFGI7k@hu-ashoraj-lv.qualcomm.com/
>>
>>
>>
>> RFC:
>> https://lore.kernel.org/all/20260929074659.2587216-1-pierre.gondois@arm.com/#t
>> V1:
>> https://lore.kernel.org/all/20261019145643.1877246-1-pierre.gondois@arm.com/
>> - Corrections from Jonathan's review
>> - New patch:
>> [PATCH v2 4/6] EDAC/ghes: Extract error report initialization
>> - Last patch not in RFC as it has been reviewed by Jonathan@
>> [PATCH v2 6/6] ACPI: extlog: add Memory Error Section 2 trace event
>> V2:
>> - Updated ghes_edac_init_error() to ghes_edac_init_error_desc(),
>> which now only acts on the input "struct edac_raw_error_desc"
>> + added lockdep_assert_held() to ghes_edac_init_error_desc()
>> - Accumulate failures with "queued |=" in ghes_do_proc()
>> - New PATCH:
>> [PATCH v3 5/7] ACPI: APEI: Extract common memory failure handling
>>
>> Pierre Gondois (7):
>> cper: use BIT_ULL() for processor and memory validation bits
>> cper: add Memory Error Section 2 structures
>> cper: add helpers to handle Memory Error Section 2
>> EDAC/ghes: Extract error report initialization
>> ACPI: APEI: Extract common memory failure handling
>> ACPI: APEI: add separate Memory Error Section 2 handlers
>> ACPI: extlog: add Memory Error Section 2 trace event
>>
>> drivers/acpi/acpi_extlog.c | 6 ++
>> drivers/acpi/apei/ghes.c | 58 +++++++++--
>> drivers/edac/ghes_edac.c | 189 +++++++++++++++++++++++++++++-------
>> drivers/firmware/efi/cper.c | 109 +++++++++++++++++++++
>> drivers/ras/ras.c | 1 +
>> include/acpi/ghes.h | 2 +
>> include/linux/cper.h | 129 +++++++++++++++++-------
>> include/ras/ras_event.h | 102 +++++++++++++++++++
>> 8 files changed, 518 insertions(+), 78 deletions(-)
>>
>> --
>> 2.43.0
prev parent reply other threads:[~2026-11-09 10:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 11:03 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
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 [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=62430a5e-1e43-45de-9f8b-f0fdc826f38b@arm.com \
--to=pierre.gondois@arm.com \
--cc=acpica-devel@lists.linux.dev \
--cc=ardb@kernel.org \
--cc=ashok.raj@oss.qualcomm.com \
--cc=bp@alien8.de \
--cc=broonie@kernel.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®