From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>
Subject: [PATCH 0/6] x86: Introduce MSR_ARCH_CAPS into featuresets
Date: Mon, 15 May 2023 15:42:53 +0100 [thread overview]
Message-ID: <20230515144259.1009245-1-andrew.cooper3@citrix.com> (raw)
Also cleanup of the various special cases we've already got. No practical
change to a system, but this is the trimmed view of the featuresets on a
Cascade Lake CPU with the series in place.
KEY ... 10Al 10Ah
Static sets:
Known ... 01beffff:00000000
Special ... 00080004:00000000
PV Max ... 011ae17f:00000000
PV Default ... 011ae17f:00000000
HVM Shadow Max ... 011ae17f:00000000
HVM Shadow Default ... 011ae17f:00000000
HVM Hap Max ... 011ae17f:00000000
HVM Hap Default ... 011ae17f:00000000
Dynamic sets:
Raw ... 000aacab:00000000
Host ... 000aacab:00000000
PV Default ... 00000000:00000000
HVM Default ... 00000000:00000000
PV Max ... 000aa02b:00000000
HVM Max ... 000aa02b:00000000
Andrew Cooper (6):
x86/boot: Rework dom0 feature configuration
x86/boot: Adjust MSR_ARCH_CAPS handling for the Host policy
x86/cpu-policy: Infrastructure for MSR_ARCH_CAPS
x86/cpu-policy: MSR_ARCH_CAPS feature names
x86/boot: Record MSR_ARCH_CAPS for the Raw and Host CPU policy
x86/boot: Expose MSR_ARCH_CAPS data in guest max policies
tools/misc/xen-cpuid.c | 23 ++++++
xen/arch/x86/cpu-policy.c | 83 ++++++++++-----------
xen/arch/x86/cpu/common.c | 5 ++
xen/include/public/arch-x86/cpufeatureset.h | 27 +++++++
xen/include/xen/lib/x86/cpu-policy.h | 18 ++---
xen/lib/x86/cpuid.c | 11 ++-
xen/tools/gen-cpuid.py | 3 +
7 files changed, 117 insertions(+), 53 deletions(-)
--
2.30.2
next reply other threads:[~2023-05-15 14:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 14:42 Andrew Cooper [this message]
2023-05-15 14:42 ` [PATCH 1/6] x86/boot: Rework dom0 feature configuration Andrew Cooper
2023-05-16 7:58 ` Jan Beulich
2023-05-16 9:45 ` Andrew Cooper
2023-05-16 11:43 ` Jan Beulich
2023-05-15 14:42 ` [PATCH 2/6] x86/boot: Adjust MSR_ARCH_CAPS handling for the Host policy Andrew Cooper
2023-05-16 11:47 ` Jan Beulich
2023-05-15 14:42 ` [PATCH 3/6] x86/cpu-policy: Infrastructure for MSR_ARCH_CAPS Andrew Cooper
2023-05-16 12:02 ` Jan Beulich
2023-05-19 15:36 ` Andrew Cooper
2023-05-22 7:18 ` Jan Beulich
2023-05-15 14:42 ` [PATCH 4/6] x86/cpu-policy: MSR_ARCH_CAPS feature names Andrew Cooper
2023-05-16 12:27 ` Jan Beulich
2023-05-16 12:56 ` Andrew Cooper
2023-05-16 13:11 ` Jan Beulich
2023-05-15 14:42 ` [PATCH 5/6] x86/boot: Record MSR_ARCH_CAPS for the Raw and Host CPU policy Andrew Cooper
2023-05-16 12:53 ` Jan Beulich
2023-05-16 12:59 ` Andrew Cooper
2023-05-15 14:42 ` [PATCH 6/6] x86/boot: Expose MSR_ARCH_CAPS data in guest max policies Andrew Cooper
2023-05-16 13:06 ` Jan Beulich
2023-05-16 13:51 ` Andrew Cooper
2023-05-16 14:06 ` Jan Beulich
2023-05-16 14:16 ` Andrew Cooper
2023-05-16 14:53 ` Jan Beulich
2023-05-16 19:31 ` Andrew Cooper
2023-05-17 9:20 ` Jan Beulich
2023-05-19 15:52 ` Andrew Cooper
2023-05-22 7:31 ` Jan Beulich
2023-05-22 14:02 ` Andrew Cooper
2023-05-16 14:58 ` Jan Beulich
2023-05-19 15:52 ` Andrew Cooper
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=20230515144259.1009245-1-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.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.