From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, bp@suse.de,
rientjes@google.com,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: [PATCH v3 0/2] x86/CPU/AMD: Add support for Extended Topology Enumeration
Date: Fri, 27 Apr 2018 16:47:59 -0500 [thread overview]
Message-ID: <1524865681-112110-1-git-send-email-suravee.suthikulpanit@amd.com> (raw)
Linux currently provides function detect_extended_topology()
for parsing CPUID Fn0xB and derive CPU topology information.
Therefore, also call this function in AMD code path.
Please note that this series depend on the previously submitted
series:
[PATCH v2 0/4] x86/CPU: Update AMD Last-Level-Cache Information
(https://lkml.org/lkml/2018/4/27/1112)
Thanks,
Suravee
Changes from v2 (https://lkml.org/lkml/2018/4/4/55)
* 2/2: Fix typo in comment.
Suravee Suthikulpanit (2):
x86/CPU: Modify detect_extended_topology() to return result
x86/CPU/AMD: Derive CPU topology from CPUID Fn0xB when available
arch/x86/include/asm/processor.h | 2 +-
arch/x86/kernel/cpu/amd.c | 11 ++++++++++-
arch/x86/kernel/cpu/topology.c | 8 ++++----
3 files changed, 15 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2018-04-27 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 21:47 Suravee Suthikulpanit [this message]
2018-04-27 21:48 ` [PATCH v3 1/2] x86/CPU: Modify detect_extended_topology() to return result Suravee Suthikulpanit
2018-05-12 21:11 ` [tip:x86/cpu] " tip-bot for Suravee Suthikulpanit
2018-04-27 21:48 ` [PATCH v3 2/2] x86/CPU/AMD: Derive CPU topology from CPUID Fn0xB when available Suravee Suthikulpanit
2018-05-12 21:12 ` [tip:x86/cpu] x86/CPU/AMD: Derive CPU topology from CPUID function 0xB " tip-bot for Suravee Suthikulpanit
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=1524865681-112110-1-git-send-email-suravee.suthikulpanit@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®