aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/kvm/Makefile
diff options
context:
space:
mode:
authorBen Gardon <bgardon@google.com>2022-06-13 21:25:21 +0000
committerPaolo Bonzini <pbonzini@redhat.com>2022-06-24 04:51:49 -0400
commit084cc29f8bbb034cf30a7ee07a816c115e0c28df (patch)
tree8324b06915b515128d5490888e78de420e18ae20 /tools/testing/selftests/kvm/Makefile
parentKVM: x86: Fix errant brace in KVM capability handling (diff)
downloadlinux-dev-084cc29f8bbb034cf30a7ee07a816c115e0c28df.tar.xz
linux-dev-084cc29f8bbb034cf30a7ee07a816c115e0c28df.zip
KVM: x86/MMU: Allow NX huge pages to be disabled on a per-vm basis
In some cases, the NX hugepage mitigation for iTLB multihit is not needed for all guests on a host. Allow disabling the mitigation on a per-VM basis to avoid the performance hit of NX hugepages on trusted workloads. In order to disable NX hugepages on a VM, ensure that the userspace actor has permission to reboot the system. Since disabling NX hugepages would allow a guest to crash the system, it is similar to reboot permissions. Ideally, KVM would require userspace to prove it has access to KVM's nx_huge_pages module param, e.g. so that userspace can opt out without needing full reboot permissions. But getting access to the module param file info is difficult because it is buried in layers of sysfs and module glue. Requiring CAP_SYS_BOOT is sufficient for all known use cases. Suggested-by: Jim Mattson <jmattson@google.com> Reviewed-by: David Matlack <dmatlack@google.com> Reviewed-by: Peter Xu <peterx@redhat.com> Signed-off-by: Ben Gardon <bgardon@google.com> Message-Id: <20220613212523.3436117-9-bgardon@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/testing/selftests/kvm/Makefile')
0 files changed, 0 insertions, 0 deletions