From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Shuai Xue <xueshuai@linux.alibaba.com>,
bp@alien8.de, tony.luck@intel.com
Cc: yazen.ghannam@amd.com, tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
baolin.wang@linux.alibaba.com, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mce/amd: init mce severity to handle deferred memory failure
Date: Tue, 9 May 2023 10:25:09 -0400 [thread overview]
Message-ID: <f629820c-50cf-7366-975e-68215b3f2bc5@amd.com> (raw)
In-Reply-To: <20230425121829.61755-1-xueshuai@linux.alibaba.com>
On 4/25/23 8:18 AM, Shuai Xue wrote:
> When a deferred UE error is detected, e.g by background patrol scruber, it
> will be handled in APIC interrupt handler amd_deferred_error_interrupt().
> The handler will collect MCA banks, init mce struct and process it by
> nofitying the registered MCE decode chain.
>
> The uc_decode_notifier, one of MCE decode chain, will process memory
> failure but only limit to MCE_AO_SEVERITY and MCE_DEFERRED_SEVERITY.
> However, APIC interrupt handler does not init mce severity and the
> uninitialized severity is 0 (MCE_NO_SEVERITY).
>
> To handle the deferred memory failure case, init mce severity when logging
> MCA banks.
>
> Signed-off-by: Shuai Xue <xueshuai@linux.alibaba.com>
>
Hi Shuai Xue,
I think this patch is fair to do. But it won't have the intended effect
in practice.
The value in MCA_ADDR for DRAM ECC errors will be a memory controller
"normalized address". This is not a system physical address that the OS
can use to take action.
The mce_usable_address() function needs to be updated to handle this.
I'll send a patchset this week to do so. Afterwards, the
uc_decode_notifier will not attempt to handle these errors.
Thanks,
Yazen
next prev parent reply other threads:[~2023-05-09 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 12:18 [PATCH] x86/mce/amd: init mce severity to handle deferred memory failure Shuai Xue
2023-05-09 14:25 ` Yazen Ghannam [this message]
2023-05-10 2:17 ` Shuai Xue
2023-05-10 13:59 ` Yazen Ghannam
2024-04-18 8:42 ` Ruidong Tian
2024-04-18 13:23 ` Yazen Ghannam
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=f629820c-50cf-7366-975e-68215b3f2bc5@amd.com \
--to=yazen.ghannam@amd.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xueshuai@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).