summaryrefslogtreecommitdiff
path: root/scripts/generate_rust_analyzer.py
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2025-06-10 16:20:06 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-08-15 12:17:07 +0200
commit3588b0eb10f3797c295f281977b84c9a0cd10fe5 (patch)
treeac8d4efa218800368639bfbc41234edeb0856b2e /scripts/generate_rust_analyzer.py
parent39d7d58179012a978f5432c25cdf613659f873c0 (diff)
KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported
commit 17ec2f965344ee3fd6620bef7ef68792f4ac3af0 upstream. Let the guest set DEBUGCTL.RTM_DEBUG if RTM is supported according to the guest CPUID model, as debug support is supposed to be available if RTM is supported, and there are no known downsides to letting the guest debug RTM aborts. Note, there are no known bug reports related to RTM_DEBUG, the primary motivation is to reduce the probability of breaking existing guests when a future change adds a missing consistency check on vmcs12.GUEST_DEBUGCTL (KVM currently lets L2 run with whatever hardware supports; whoops). Note #2, KVM already emulates DR6.RTM, and doesn't restrict access to DR7.RTM. Fixes: 83c529151ab0 ("KVM: x86: expose Intel cpu new features (HLE, RTM) to guest") Cc: stable@vger.kernel.org Link: https://lore.kernel.org/r/20250610232010.162191-5-seanjc@google.com Signed-off-by: Sean Christopherson <seanjc@google.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions