aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/net/lib/py/utils.py
diff options
context:
space:
mode:
authorSean Christopherson <[email protected]>2025-02-27 22:24:07 +0000
committerSean Christopherson <[email protected]>2025-02-28 17:17:45 +0000
commitd0eac42f5cecce009d315655bee341304fbe075e (patch)
tree51e863d02d6587bd540da034c14ac54345878230 /tools/testing/selftests/net/lib/py/utils.py
parentKVM: SVM: Drop DEBUGCTL[5:2] from guest's effective value (diff)
downloadkernel-d0eac42f5cecce009d315655bee341304fbe075e.tar.gz
kernel-d0eac42f5cecce009d315655bee341304fbe075e.zip
KVM: SVM: Suppress DEBUGCTL.BTF on AMD
Mark BTF as reserved in DEBUGCTL on AMD, as KVM doesn't actually support BTF, and fully enabling BTF virtualization is non-trivial due to interactions with the emulator, guest_debug, #DB interception, nested SVM, etc. Don't inject #GP if the guest attempts to set BTF, as there's no way to communicate lack of support to the guest, and instead suppress the flag and treat the WRMSR as (partially) unsupported. In short, make KVM behave the same on AMD and Intel (VMX already squashes BTF). Note, due to other bugs in KVM's handling of DEBUGCTL, the only way BTF has "worked" in any capacity is if the guest simultaneously enables LBRs. Reported-by: Ravi Bangoria <[email protected]> Cc: [email protected] Reviewed-and-tested-by: Ravi Bangoria <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions