From: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
To: Pierre Gondois <pierre.gondois@arm.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>,
"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 5/6] ACPI: APEI: add separate Memory Error Section 2 handlers
Date: Mon, 19 Oct 2026 12:24:35 -0700 [thread overview]
Message-ID: <20261019122435.000079c0@oss.qualcomm.com> (raw)
In-Reply-To: <20261019145643.1877246-6-pierre.gondois@arm.com>
On Mon, 19 Oct 2026 16:56:12 +0200
Pierre Gondois <pierre.gondois@arm.com> 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.
>
> Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
A few trivial things inline.
Otherwise I'm fine with this though as you noted before the duplicating
is a bit annoying.
> ---
> drivers/acpi/apei/ghes.c | 49 ++++++++++++-
> drivers/edac/ghes_edac.c | 150 +++++++++++++++++++++++++++++++++++++++
> include/acpi/ghes.h | 2 +
> 3 files changed, 200 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
> index fe10ab0e02f6..c7fb15543b56 100644
> --- a/drivers/acpi/apei/ghes.c
> +++ b/drivers/acpi/apei/ghes.c
> diff --git a/drivers/edac/ghes_edac.c b/drivers/edac/ghes_edac.c
> index d80c88818691..b18460ba8f40 100644
> --- a/drivers/edac/ghes_edac.c
> +++ b/drivers/edac/ghes_edac.c
> +
> +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;
> + unsigned long sev = val;
> + struct ghes_pvt *pvt;
> + unsigned long flags;
> + char *p;
> +
> + /*
> + * We can do the locking below because GHES defers error processing
> + * from NMI to IRQ context. Whenever that changes, we'd at least
> + * know.
> + */
> + if (WARN_ON_ONCE(in_nmi()))
> + return NOTIFY_OK;
> +
> + spin_lock_irqsave(&ghes_lock, flags);
Perhaps use a guard so you can simplify error paths a little.
> +
> + pvt = ghes_pvt;
> + if (!pvt)
> + goto unlock;
> +
> + mci = pvt->mci;
> + e = &mci->error_desc;
> +
> + /* Cleans the error report buffer */
> + memset(e, 0, sizeof(*e));
> + e->error_count = 1;
> + e->grain = 1;
> + e->msg = pvt->msg;
> + e->other_detail = pvt->other_detail;
> + e->top_layer = -1;
> + e->mid_layer = -1;
> + e->low_layer = -1;
> + *pvt->other_detail = '\0';
> + *pvt->msg = '\0';
> +
> + switch (sev) {
> + case GHES_SEV_CORRECTED:
> + e->type = HW_EVENT_ERR_CORRECTED;
> + break;
> + case GHES_SEV_RECOVERABLE:
> + e->type = HW_EVENT_ERR_UNCORRECTED;
> + break;
> + case GHES_SEV_PANIC:
> + e->type = HW_EVENT_ERR_FATAL;
> + break;
> + default:
> + case GHES_SEV_NO:
> + e->type = HW_EVENT_ERR_INFO;
> + }
> +
Almost everything down to here is not memerr2 specific maybe factor
out an initialization helper for the edac structure?
> + edac_dbg(1, "error validation_bits: 0x%08llx\n",
> + (long long)mem_err->validation_bits);
> +
> + /* Error type, mapped on e->msg */
> + if (mem_err->validation_bits & CPER_MEM2_VALID_ERROR_TYPE) {
> + u8 etype = mem_err->error_type;
> +
> + p = pvt->msg;
> + p += snprintf(p, sizeof(pvt->msg), "%s", cper_mem_err_type_str(etype));
> + } else {
> + strscpy(pvt->msg, "unknown error");
> + }
> +
> + /* Error address */
> + if (mem_err->validation_bits & CPER_MEM2_VALID_PA) {
> + e->page_frame_number = PHYS_PFN(mem_err->physical_addr);
> + e->offset_in_page = offset_in_page(mem_err->physical_addr);
> + }
> +
> + /* Error grain */
> + if (mem_err->validation_bits & CPER_MEM2_VALID_PA_MASK)
> + e->grain = ~mem_err->physical_addr_mask + 1;
> +
> + /* 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);
> + 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);
> + if (dimm) {
> + e->top_layer = dimm->idx;
> + strscpy(e->label, dimm->label);
> + }
> + }
> + if (p > e->location)
> + *(p - 1) = '\0';
> +
> + if (!*e->label)
> + strscpy(e->label, "unknown memory");
> +
> + /* All other fields are mapped on e->other_detail */
> + p = pvt->other_detail;
> + p += print_mem_error2_other_detail(mem_err, p, e->location, OTHER_DETAIL_LEN);
> + if (p > pvt->other_detail)
> + *(p - 1) = '\0';
> +
> + edac_raw_mc_handle_error(e);
> +
> +unlock:
> + spin_unlock_irqrestore(&ghes_lock, flags);
> +
> + return NOTIFY_OK;
> +}
next prev parent reply other threads:[~2026-10-19 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 14:56 [PATCH 0/6] CPER: Add Memory Error Section 2 support Pierre Gondois
2026-10-19 14:56 ` [PATCH 1/6] ACPI: extlog: fix extlog_mem_event build issue Pierre Gondois
2026-10-19 16:36 ` Jonathan Cameron
2026-10-19 17:55 ` Pierre Gondois
2026-10-19 14:56 ` [PATCH 2/6] cper: add Memory Error Section 2 structures Pierre Gondois
2026-10-19 18:16 ` Jonathan Cameron
2026-10-19 14:56 ` [PATCH 3/6] cper: use BIT_ULL() for processor and memory validation bits Pierre Gondois
2026-10-19 18:21 ` Jonathan Cameron
2026-10-19 14:56 ` [PATCH 4/6] cper: add helpers to handle Memory Error Section 2 Pierre Gondois
2026-10-19 19:13 ` Jonathan Cameron
2026-10-19 14:56 ` [PATCH 5/6] ACPI: APEI: add separate Memory Error Section 2 handlers Pierre Gondois
2026-10-19 19:24 ` Jonathan Cameron [this message]
2026-10-19 14:56 ` [RFC PATCH 6/6] ACPI: extlog: add Memory Error Section 2 trace event Pierre Gondois
2026-10-19 19:28 ` Jonathan Cameron
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=20261019122435.000079c0@oss.qualcomm.com \
--to=jonathan.cameron@oss.qualcomm.com \
--cc=acpica-devel@lists.linux.dev \
--cc=ardb@kernel.org \
--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=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=pierre.gondois@arm.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 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.