From: Jon Kohler <jon@nutanix.com>
To: pbonzini@redhat.com, zhao1.liu@intel.com, qemu-devel@nongnu.org,
pawan.kumar.gupta@linux.intel.com
Cc: Jon Kohler <jon@nutanix.com>
Subject: [PATCH 2/5] target/i386: introduce SapphireRapids-v5 to expose ITS_NO
Date: Thu, 6 Nov 2025 10:46:22 -0700 [thread overview]
Message-ID: <20251106174626.49930-3-jon@nutanix.com> (raw)
In-Reply-To: <20251106174626.49930-1-jon@nutanix.com>
Expose ITS_NO by default, as users using Sapphire Rapids and higher
CPU models would not be able to live migrate to lower CPU hosts due to
missing features. In that case, they would not be vulnerable to ITS.
its-no was originally added on [1], but needs to be exposed on the
individual CPU models for the guests to see by default.
[1] 74978391b2da ("target/i386: Make ITS_NO available to guests")
Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Signed-off-by: Jon Kohler <jon@nutanix.com>
---
target/i386/cpu.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index 6417775786..e579b790e0 100644
--- a/target/i386/cpu.c
+++ b/target/i386/cpu.c
@@ -5111,6 +5111,15 @@ static const X86CPUDefinition builtin_x86_defs[] = {
{ /* end of list */ },
}
},
+ {
+ .version = 5,
+ .note = "with ITS_NO",
+ .cache_info = &xeon_spr_cache_info,
+ .props = (PropValue[]) {
+ { "its-no", "on" },
+ { /* end of list */ },
+ }
+ },
{ /* end of list */ }
}
},
--
2.43.0
next prev parent reply other threads:[~2025-11-06 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 17:46 [PATCH 0/5] target/i386: introduce ITS_NO to several models Jon Kohler
2025-11-06 17:46 ` [PATCH 1/5] target/i386: Add MSR_IA32_ARCH_CAPABILITIES ITS_NO Jon Kohler
2025-11-06 17:46 ` Jon Kohler [this message]
2025-11-06 17:46 ` [PATCH 3/5] target/i386: introduce GraniteRapids-v4 to expose ITS_NO Jon Kohler
2025-11-06 17:46 ` [PATCH 4/5] target/i386: introduce SierraForest-v4 " Jon Kohler
2025-11-06 17:46 ` [PATCH 5/5] target/i386: introduce ClearwaterForest-v2 " Jon Kohler
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=20251106174626.49930-3-jon@nutanix.com \
--to=jon@nutanix.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhao1.liu@intel.com \
/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).