linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
To: <x86@kernel.org>, <linux-edac@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: Tony Luck <tony.luck@intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H . Peter Anvin" <hpa@zytor.com>,
	James Morse <james.morse@arm.com>,
	Robert Richter <rric@kernel.org>,
	Yazen Ghannam <yazen.ghannam@amd.com>,
	Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
Subject: [PATCH v3 0/4] x86/mce, EDAC/mce_amd: Support extended MCA_ADDR address on SMCA systems
Date: Fri, 11 Feb 2022 16:34:38 -0600	[thread overview]
Message-ID: <20220211223442.254489-1-Smita.KoralahalliChannabasappa@amd.com> (raw)

This series of patches adds support for extended physical address on newer
AMD processors such as AMD 'Milan'. It also, suggests to cache
MCA_CONFIG[McaX] similar to MCA_CONFIG[McaLsbInStatusSupported] to avoid
reading MCA_CONFIG register each time.

The first patch defines a separate helper function to extract
MCA_ADDR[ErrorAddr].

The second patch adds support for extended ErrorAddr bits in MCA_ADDR.

Third patch, caches MCA_CONFIG[McaX] similar to
MCA_CONFIG[McaLsbInStatusSupported] in the existing mce_bank struct.

Last patch, fixes unnecessary padding in mce_bank struct.

Link:
https://lkml.kernel.org/r/20210625013553.231528-1-Smita.KoralahalliChannabasappa@amd.com

Smita Koralahalli (4):
  x86/mce: Define function to extract ErrorAddr from MCA_ADDR
  x86/mce: Add support for Extended Physical Address MCA changes
  x86/mce, EDAC/mce_amd: Cache MCA_CONFIG[McaX] in struct mce_bank
  x86/mce: Avoid unnecessary padding in struct mce_bank

 arch/x86/include/asm/mce.h         | 14 +++----
 arch/x86/kernel/cpu/mce/amd.c      | 59 +++++++++++++++++++++++-------
 arch/x86/kernel/cpu/mce/core.c     | 20 +++-------
 arch/x86/kernel/cpu/mce/internal.h | 26 +++++++++++++
 arch/x86/kernel/cpu/mce/severity.c |  6 +--
 drivers/edac/mce_amd.c             |  5 +--
 6 files changed, 86 insertions(+), 44 deletions(-)

-- 
2.17.1


             reply	other threads:[~2022-02-11 22:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 22:34 Smita Koralahalli [this message]
2022-02-11 22:34 ` [PATCH v3 1/4] x86/mce: Define function to extract ErrorAddr from MCA_ADDR Smita Koralahalli
2022-02-22 15:35   ` Borislav Petkov
2022-02-22 20:34     ` Koralahalli Channabasappa, Smita
2022-02-11 22:34 ` [PATCH v3 2/4] x86/mce: Add support for Extended Physical Address MCA changes Smita Koralahalli
2022-02-11 22:34 ` [PATCH v3 3/4] x86/mce, EDAC/mce_amd: Cache MCA_CONFIG[McaX] in struct mce_bank Smita Koralahalli
2022-02-22 15:35   ` Borislav Petkov
2022-02-22 20:47     ` Koralahalli Channabasappa, Smita
2022-02-22 21:15       ` Borislav Petkov
2022-02-23 22:25         ` Koralahalli Channabasappa, Smita
2022-02-11 22:34 ` [PATCH v3 4/4] x86/mce: Avoid unnecessary padding " Smita Koralahalli
2022-02-22 15:36   ` Borislav Petkov
2022-02-22 21:02     ` Koralahalli Channabasappa, Smita

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=20220211223442.254489-1-Smita.KoralahalliChannabasappa@amd.com \
    --to=smita.koralahallichannabasappa@amd.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rric@kernel.org \
    --cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).