From: Yazen Ghannam <yazen.ghannam@amd.com>
To: <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>,
<xueshuai@linux.alibaba.com>, <baolin.wang@linux.alibaba.com>,
Yazen Ghannam <yazen.ghannam@amd.com>
Subject: [PATCH 0/3] Properly check for usable addresses on AMD
Date: Tue, 13 Jun 2023 09:11:39 -0500 [thread overview]
Message-ID: <20230613141142.36801-1-yazen.ghannam@amd.com> (raw)
Hi all,
This set adds proper checks for usable addresses on AMD systems.
Patch 1 creates helper functions for memory error checks that will be
used in the second patch.
Patch 2 adds the proper usable address checks.
Patch 3 restructures the current usable address function to call out to
vendor-specific helpers.
I don't think these need 'stable' backports, since there isn't an urgent
issue to be fixed. But I can include 'stable' if there's interest.
Thanks,
Yazen
Yazen Ghannam (3):
x86/MCE/AMD: Split amd_mce_is_memory_error()
x86/mce: Define amd_mce_usable_address()
x86/mce: Fixup mce_usable_address()
arch/x86/include/asm/mce.h | 2 +-
arch/x86/kernel/cpu/mce/amd.c | 68 +++++++++++++++++++++++++++---
arch/x86/kernel/cpu/mce/core.c | 32 +++++---------
arch/x86/kernel/cpu/mce/intel.c | 20 +++++++++
arch/x86/kernel/cpu/mce/internal.h | 4 ++
5 files changed, 99 insertions(+), 27 deletions(-)
--
2.34.1
next reply other threads:[~2023-06-13 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:11 Yazen Ghannam [this message]
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-06-13 14:11 ` [PATCH 2/3] x86/mce: Define amd_mce_usable_address() Yazen Ghannam
2023-06-14 2:19 ` Shuai Xue
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-06-13 14:11 ` [PATCH 3/3] x86/mce: Fixup mce_usable_address() 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=20230613141142.36801-1-yazen.ghannam@amd.com \
--to=yazen.ghannam@amd.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=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