* ITLB Multihit mitigation status report is confusing.
@ 2021-11-07 16:00 Lucius User
0 siblings, 0 replies; only message in thread
From: Lucius User @ 2021-11-07 16:00 UTC (permalink / raw)
To: linux-kernel
Hi all.
On a cpu that is vulnerable to iTLB multihit, with VMX enabled in bios and no vms running, the kernel reports the mitigation status as "KVM: Mitigation: VMX disabled". Once a vm starts running, the report changes to "KVM: Vulnerable". Shouldn't the VMX disabled status refer to a situation when VMX is completely disabled via bios, not merely not in use right now?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-11-07 16:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-07 16:00 ITLB Multihit mitigation status report is confusing Lucius User
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).