From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Yazen Ghannam <yazen.ghannam@amd.com>, linux-edac@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, tony.luck@intel.com,
x86@kernel.org, muralidhara.mk@amd.com,
joao.m.martins@oracle.com, william.roche@oracle.com,
boris.ostrovsky@oracle.com, john.allen@amd.com,
baolin.wang@linux.alibaba.com
Subject: Re: [PATCH 2/3] x86/mce: Define amd_mce_usable_address()
Date: Wed, 14 Jun 2023 10:19:13 +0800 [thread overview]
Message-ID: <31fdaacc-cc2b-5ea5-8a0e-e5ccfe674834@linux.alibaba.com> (raw)
In-Reply-To: <20230613141142.36801-3-yazen.ghannam@amd.com>
On 2023/6/13 22:11, Yazen Ghannam wrote:
> Currently, all valid MCA_ADDR values are assumed to be usable on AMD
> systems. However, this is not correct in most cases. Notifiers expecting
> usable addresses may then operate on inappropriate values.
>
> Define a helper function to do AMD-specific checks for a usable memory
> address. List out all known cases.
>
> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
> ---
> arch/x86/kernel/cpu/mce/amd.c | 38 ++++++++++++++++++++++++++++++
> arch/x86/kernel/cpu/mce/core.c | 3 +++
> arch/x86/kernel/cpu/mce/internal.h | 2 ++
> 3 files changed, 43 insertions(+)
>
> diff --git a/arch/x86/kernel/cpu/mce/amd.c b/arch/x86/kernel/cpu/mce/amd.c
> index 1ccfb0c9257f..ca79fa10b844 100644
> --- a/arch/x86/kernel/cpu/mce/amd.c
> +++ b/arch/x86/kernel/cpu/mce/amd.c
> @@ -746,6 +746,44 @@ bool amd_mce_is_memory_error(struct mce *m)
> return legacy_mce_is_memory_error(m);
> }
>
> +/*
> + * AMD systems do not have an explicit indicator that the value in MCA_ADDR is
> + * a system physical address. Therefore individual cases need to be detected.
> + * Future cases and checks will be added as needed.
> + *
> + * 1) General case
> + * a) Assume address is not usable.
> + * 2) "Poison" errors
> + * a) Indicated by MCA_STATUS[43]: POISON. Defined for all banks except legacy
> + * Northbridge (bank 4).
> + * b) Refers to poison consumption in the Core. Does not include "no action",
> + * "action optional", or "deferred" error severities.
> + * c) Will include a usuable address so that immediate action can be taken.
> + * 3) Northbridge DRAM ECC errors
> + * a) Reported in legacy bank 4 with XEC 8.
> + * b) MCA_STATUS[43] is *not* defined as POISON in legacy bank 4. Therefore,
> + * this bit should not be checked.
[nit]
> + *
> + * NOTE: SMCA UMC memory errors fall into case #1.
hi, Yazen
The address for SMCA UMC memory error is not system physical address, it make sense
to be not usable. But how we deal with the SMCA address? The MCE chain like
uc_decode_notifier will do a sanity check with mce_usable_address and it will not
handle SMCA address.
Thanks.
Best Regards,
Shuai
> + */
> +bool amd_mce_usable_address(struct mce *m)
> +{
> + /* Check special Northbridge case first. */
> + if (!mce_flags.smca) {
> + if (legacy_mce_is_memory_error(m))
> + return true;
> + else if (m->bank == 4)
> + return false;
> + }
> +
> + /* Check Poison bit for all other bank types. */
> + if (m->status & MCI_STATUS_POISON)
> + return true;
> +
> + /* Assume address is not usable for all others. */
> + return false;
> +}
> +
> static void __log_error(unsigned int bank, u64 status, u64 addr, u64 misc)
> {
> struct mce m;
> diff --git a/arch/x86/kernel/cpu/mce/core.c b/arch/x86/kernel/cpu/mce/core.c
> index 89e2aab5d34d..859ce20dd730 100644
> --- a/arch/x86/kernel/cpu/mce/core.c
> +++ b/arch/x86/kernel/cpu/mce/core.c
> @@ -464,6 +464,9 @@ int mce_usable_address(struct mce *m)
> if (!(m->status & MCI_STATUS_ADDRV))
> return 0;
>
> + if (m->cpuvendor == X86_VENDOR_AMD)
> + return amd_mce_usable_address(m);
> +
> /* Checks after this one are Intel/Zhaoxin-specific: */
> if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL &&
> boot_cpu_data.x86_vendor != X86_VENDOR_ZHAOXIN)
> diff --git a/arch/x86/kernel/cpu/mce/internal.h b/arch/x86/kernel/cpu/mce/internal.h
> index d2412ce2d312..0d4c5b83ed93 100644
> --- a/arch/x86/kernel/cpu/mce/internal.h
> +++ b/arch/x86/kernel/cpu/mce/internal.h
> @@ -207,6 +207,7 @@ extern bool filter_mce(struct mce *m);
>
> #ifdef CONFIG_X86_MCE_AMD
> extern bool amd_filter_mce(struct mce *m);
> +bool amd_mce_usable_address(struct mce *m);
>
> /*
> * If MCA_CONFIG[McaLsbInStatusSupported] is set, extract ErrAddr in bits
> @@ -234,6 +235,7 @@ static __always_inline void smca_extract_err_addr(struct mce *m)
>
> #else
> static inline bool amd_filter_mce(struct mce *m) { return false; }
> +static inline bool amd_mce_usable_address(struct mce *m) { return false; }
> static inline void smca_extract_err_addr(struct mce *m) { }
> #endif
>
next prev parent reply other threads:[~2023-06-14 2:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:11 [PATCH 0/3] Properly check for usable addresses on AMD Yazen Ghannam
2023-06-13 14:11 ` [PATCH 1/3] x86/MCE/AMD: Split amd_mce_is_memory_error() Yazen Ghannam
2023-06-14 2:06 ` Shuai Xue
2023-06-14 15:06 ` Yazen Ghannam
2023-06-15 2:03 ` Shuai Xue
2023-06-15 15:09 ` Yazen Ghannam
2023-10-16 13:48 ` [tip: ras/core] " tip-bot2 for Yazen Ghannam
2023-06-13 14:11 ` [PATCH 2/3] x86/mce: Define amd_mce_usable_address() Yazen Ghannam
2023-06-14 2:19 ` Shuai Xue [this message]
2023-06-14 15:09 ` Yazen Ghannam
2023-06-15 2:12 ` Shuai Xue
2023-06-15 15:15 ` Yazen Ghannam
2023-06-16 1:59 ` Shuai Xue
2023-06-16 7:46 ` William Roche
2023-10-16 13:48 ` [tip: ras/core] " tip-bot2 for Yazen Ghannam
2023-06-13 14:11 ` [PATCH 3/3] x86/mce: Fixup mce_usable_address() Yazen Ghannam
2023-10-16 13:48 ` [tip: ras/core] x86/mce: Cleanup mce_usable_address() tip-bot2 for 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=31fdaacc-cc2b-5ea5-8a0e-e5ccfe674834@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=boris.ostrovsky@oracle.com \
--cc=joao.m.martins@oracle.com \
--cc=john.allen@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muralidhara.mk@amd.com \
--cc=tony.luck@intel.com \
--cc=william.roche@oracle.com \
--cc=x86@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox