summaryrefslogtreecommitdiff
path: root/scripts/basic/split-include.c
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2026-09-30 14:21:13 -0700
committerSean Christopherson <seanjc@google.com>2026-09-30 14:22:38 -0700
commit58f4dc83da6e5baf8b9a9752e433360c6b17df38 (patch)
tree29dc3f8ed0e0dbcf37b511434e7fc8109239192a /scripts/basic/split-include.c
parentcc2b9cc15ab702a3d4ada479f129fd287e40bd7e (diff)
downloadlinux-58f4dc83da6e5baf8b9a9752e433360c6b17df38.tar.gz
linux-58f4dc83da6e5baf8b9a9752e433360c6b17df38.zip
KVM: selftests: Add module param API to check if nested virtualization is enabled
Add an API to check if the nested virtualization module param is enabled, e.g. so that tests can verify KVM's own enumeration of the corresponding CPU feature. Provide a big warning above the API to make it as obvious as possible clear that tests should use "kvm_cpu_has(X86_FEATURE_VMX) || kvm_cpu_has(X86_FEATURE_SVM)" when checking for nested virtualization. It doesn't really matter which method tests use, as KVM is supposed to keep "nested" synchronized with VMX/SVM enumeration, but make the comment super scary to try and prevent KVM selftests from having two different ways of doing the same thing. Note, the bool vs. int mess is intentional, because KVM's params are terrible. kvm_amd.ko provides an "int", while kvm_intel.ko provides a "bool". Link: https://patch.msgid.link/20260930212114.3500045-5-seanjc@google.com Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/basic/split-include.c')
0 files changed, 0 insertions, 0 deletions