From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL 3/5] target/i386: ignore ARCH_CAPABILITIES features in user mode emulation
Date: Thu, 29 Jun 2023 12:19:16 +0200 [thread overview]
Message-ID: <20230629101918.9800-4-pbonzini@redhat.com> (raw)
In-Reply-To: <20230629101918.9800-1-pbonzini@redhat.com>
ARCH_CAPABILITIES is only accessible through a read-only MSR, so it has
no impact on any user-mode operation (user-mode cannot read the MSR).
So do not bother printing warnings about it in user mode emulation.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
target/i386/cpu.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index b96a609d966..328779874f2 100644
--- a/target/i386/cpu.c
+++ b/target/i386/cpu.c
@@ -1069,6 +1069,13 @@ FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
.msr = {
.index = MSR_IA32_ARCH_CAPABILITIES,
},
+ /*
+ * FEAT_ARCH_CAPABILITIES only affects a read-only MSR, which
+ * cannot be read from user mode. Therefore, it has no impact
+ > on any user-mode operation, and warnings about unsupported
+ * features do not matter.
+ */
+ .tcg_features = ~0U,
},
[FEAT_CORE_CAPABILITY] = {
.type = MSR_FEATURE_WORD,
--
2.41.0
next prev parent reply other threads:[~2023-06-29 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 10:19 [PULL 0/5] x86, main loop changes for 2023-06-29 Paolo Bonzini
2023-06-29 10:19 ` [PULL 1/5] icount: don't adjust virtual time backwards after warp Paolo Bonzini
2023-06-29 10:19 ` [PULL 2/5] target/i386: Export MSR_ARCH_CAPABILITIES bits to guests Paolo Bonzini
2023-06-29 10:19 ` Paolo Bonzini [this message]
2023-06-29 10:19 ` [PULL 4/5] target/i386: ignore CPL0-specific features in user mode emulation Paolo Bonzini
2023-06-29 10:19 ` [PULL 5/5] target/i386: emulate 64-bit ring 0 for linux-user if LM feature is set Paolo Bonzini
2023-06-29 12:59 ` [PULL 0/5] x86, main loop changes for 2023-06-29 Richard Henderson
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=20230629101918.9800-4-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).