From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH v2 1/2] x86/Intel: Sapphire Rapids Xeons also support PPIN
Date: Thu, 20 Jan 2022 15:16:35 +0100 [thread overview]
Message-ID: <0a8981c6-b3fe-c805-f45b-b6da5d0aa1af@suse.com> (raw)
In-Reply-To: <64a5a3ac-8f4c-b13d-0b7d-4c4ec15e2721@suse.com>
This is as per Linux commit a331f5fdd36d ("x86/mce: Add Xeon Sapphire
Rapids to list of CPUs that support PPIN") just in case a subsequent
change making use of the respective new CPUID bit doesn't cover this
model.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
---
It is unclear to me whether this change is actually made obsolete by the
subsequent one adding support for the respective new CPUID bit.
It also continues to be unclear for which CPU models, if any, the
PPIN_CAP bit in PLATFORM_INFO could be used in favor of a model check.
---
v2: New.
--- a/xen/arch/x86/cpu/mcheck/mce_intel.c
+++ b/xen/arch/x86/cpu/mcheck/mce_intel.c
@@ -873,6 +873,7 @@ static void intel_init_ppin(const struct
case 0x57: /* Knights Landing */
case 0x6a: /* Icelake X */
case 0x85: /* Knights Mill */
+ case 0x8f: /* Sapphire Rapids X */
if ( (c != &boot_cpu_data && !ppin_msr) ||
rdmsr_safe(MSR_PPIN_CTL, val) )
next prev parent reply other threads:[~2022-01-20 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 14:15 [PATCH v2 0/2] x86/Intel: PPIN recognition adjustments Jan Beulich
2022-01-20 14:16 ` Jan Beulich [this message]
2022-01-26 23:01 ` [PATCH v2 1/2] x86/Intel: Sapphire Rapids Xeons also support PPIN Andrew Cooper
2022-01-27 7:42 ` Jan Beulich
2022-01-20 14:17 ` [PATCH v2 2/2] x86/Intel: use CPUID bit to determine PPIN availability Jan Beulich
2022-01-26 23:30 ` Andrew Cooper
2022-01-27 7:56 ` Jan Beulich
2022-01-27 8:15 ` Jan Beulich
2022-01-27 12:54 ` [PATCH v3] " Jan Beulich
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=0a8981c6-b3fe-c805-f45b-b6da5d0aa1af@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.