diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2024-12-22 20:59:33 +0300 | 
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-12-22 20:59:33 +0300 | 
| commit | 10b2c8a67c4b8ec15f9d07d177f63b563418e948 (patch) | |
| tree | 8979d344d5567661ef536e83d202afcc3bab2bb2 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | a066bad89c6c79890bb8f45aef8662dcd0562a62 (diff) | |
| parent | 386d69f9f29b0814881fa4f92ac7b8dfa9b4f44a (diff) | |
| download | linux-10b2c8a67c4b8ec15f9d07d177f63b563418e948.tar.xz | |
Merge tag 'kvm-x86-fixes-6.13-rcN' of https://github.com/kvm-x86/linux into HEAD
KVM x86 fixes for 6.13:
 - Disable AVIC on SNP-enabled systems that don't allow writes to the virtual
   APIC page, as such hosts will hit unexpected RMP #PFs in the host when
   running VMs of any flavor.
 - Fix a WARN in the hypercall completion path due to KVM trying to determine
   if a guest with protected register state is in 64-bit mode (KVM's ABI is to
   assume such guests only make hypercalls in 64-bit mode).
 - Allow the guest to write to supported bits in MSR_AMD64_DE_CFG to fix a
   regression with Windows guests, and because KVM's read-only behavior appears
   to be entirely made up.
 - Treat TDP MMU faults as spurious if the faulting access is allowed given the
   existing SPTE.  This fixes a benign WARN (other than the WARN itself) due to
   unexpectedly replacing a writable SPTE with a read-only SPTE.
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions
