aboutsummaryrefslogtreecommitdiff
path: root/Documentation/admin-guide
diff options
context:
space:
mode:
authorGravatar Pawan Gupta <pawan.kumar.gupta@linux.intel.com> 2024-03-11 12:29:43 -0700
committerGravatar Dave Hansen <dave.hansen@linux.intel.com> 2024-03-11 13:13:28 -0700
commite95df4ec0c0c9791941f112db699fae794b9862a (patch)
tree273916b25df45c01c17612b7715a432f40444604 /Documentation/admin-guide
parentLinux 6.8-rc7 (diff)
downloadlinux-e95df4ec0c0c9791941f112db699fae794b9862a.tar.gz
linux-e95df4ec0c0c9791941f112db699fae794b9862a.tar.bz2
linux-e95df4ec0c0c9791941f112db699fae794b9862a.zip
x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set
Currently MMIO Stale Data mitigation for CPUs not affected by MDS/TAA is to only deploy VERW at VMentry by enabling mmio_stale_data_clear static branch. No mitigation is needed for kernel->user transitions. If such CPUs are also affected by RFDS, its mitigation may set X86_FEATURE_CLEAR_CPU_BUF to deploy VERW at kernel->user and VMentry. This could result in duplicate VERW at VMentry. Fix this by disabling mmio_stale_data_clear static branch when X86_FEATURE_CLEAR_CPU_BUF is enabled. Signed-off-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com>
Diffstat (limited to 'Documentation/admin-guide')
0 files changed, 0 insertions, 0 deletions