linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yazen Ghannam <Yazen.Ghannam@amd.com>
To: x86@kernel.org
Cc: Yazen Ghannam <Yazen.Ghannam@amd.com>,
	linux-kernel@vger.kernel.org,
	Smita.KoralahalliChannabasappa@amd.com,
	linux-edac@vger.kernel.org, puwen@hygon.cn, kim.phillips@amd.com,
	thomas.lendacky@amd.com, wei.huang2@amd.com
Subject: [PATCH 0/4] Set and use cpu_die_id on AMD-based systems
Date: Mon,  9 Nov 2020 21:06:55 +0000	[thread overview]
Message-ID: <20201109210659.754018-1-Yazen.Ghannam@amd.com> (raw)

From: Yazen Ghannam <yazen.ghannam@amd.com>

AMD-based systems currently use a "NodeId" when referencing a
software-visible hardware structure. This may be referred to as a "Die"
in x86 documentation, "Node" in some AMD documentation, and "Package" in
Linux documentation.

Recently a cpu_die_id value was added to struct cpuinfo_x86. This value
can be used on AMD-based systems rather than using an AMD-specific value
throughout the kernel.

This set is based on patches 1-3 from the following set.
https://lkml.kernel.org/r/20200903200144.310991-1-Yazen.Ghannam@amd.com

Thanks,
Yazen

Yazen Ghannam (4):
  x86/CPU/AMD: Save AMD NodeId as cpu_die_id
  x86/CPU/AMD: Remove amd_get_nb_id()
  EDAC/mce_amd: Use struct cpuinfo_x86.cpu_die_id for AMD NodeId
  x86/topology: Set cpu_die_id only if DIE_TYPE found

 Documentation/x86/topology.rst   |  9 +++++++++
 arch/x86/events/amd/core.c       |  2 +-
 arch/x86/include/asm/cacheinfo.h |  4 ++--
 arch/x86/include/asm/processor.h |  2 --
 arch/x86/kernel/amd_nb.c         |  4 ++--
 arch/x86/kernel/cpu/amd.c        | 17 +++++------------
 arch/x86/kernel/cpu/cacheinfo.c  |  8 ++++----
 arch/x86/kernel/cpu/hygon.c      | 11 +++++------
 arch/x86/kernel/cpu/mce/amd.c    |  4 ++--
 arch/x86/kernel/cpu/mce/inject.c |  4 ++--
 arch/x86/kernel/cpu/topology.c   | 10 ++++++++--
 drivers/edac/amd64_edac.c        |  4 ++--
 drivers/edac/mce_amd.c           |  4 ++--
 13 files changed, 44 insertions(+), 39 deletions(-)

-- 
2.25.1


             reply	other threads:[~2020-11-09 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 21:06 Yazen Ghannam [this message]
2020-11-09 21:06 ` [PATCH 1/4] x86/CPU/AMD: Save AMD NodeId as cpu_die_id Yazen Ghannam
2020-11-19 11:29   ` [tip: x86/cpu] " tip-bot2 for Yazen Ghannam
2020-11-09 21:06 ` [PATCH 2/4] x86/CPU/AMD: Remove amd_get_nb_id() Yazen Ghannam
2020-11-19 11:29   ` [tip: x86/cpu] " tip-bot2 for Yazen Ghannam
2020-11-09 21:06 ` [PATCH 3/4] EDAC/mce_amd: Use struct cpuinfo_x86.cpu_die_id for AMD NodeId Yazen Ghannam
2020-11-19 11:29   ` [tip: x86/cpu] " tip-bot2 for Yazen Ghannam
2020-11-09 21:06 ` [PATCH 4/4] x86/topology: Set cpu_die_id only if DIE_TYPE found Yazen Ghannam
2020-11-19 11:29   ` [tip: x86/cpu] " 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=20201109210659.754018-1-Yazen.Ghannam@amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=Smita.KoralahalliChannabasappa@amd.com \
    --cc=kim.phillips@amd.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=puwen@hygon.cn \
    --cc=thomas.lendacky@amd.com \
    --cc=wei.huang2@amd.com \
    --cc=x86@kernel.org \
    /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).