diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2024-12-19 15:50:06 +0300 | 
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-12-19 15:50:06 +0300 | 
| commit | a066bad89c6c79890bb8f45aef8662dcd0562a62 (patch) | |
| tree | f416c9158b826cf8c34147561677974580ae7b23 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8 (diff) | |
| parent | 9af04539d474dda4984ff4909d4568e6123c8cba (diff) | |
| download | linux-a066bad89c6c79890bb8f45aef8662dcd0562a62.tar.xz | |
Merge tag 'kvm-selftests-treewide-6.14' of https://github.com/kvm-x86/linux into HEAD
KVM selftests "tree"-wide changes for 6.14:
 - Rework vcpu_get_reg() to return a value instead of using an out-param, and
   update all affected arch code accordingly.
 - Convert the max_guest_memory_test into a more generic mmu_stress_test.
   The basic gist of the "conversion" is to have the test do mprotect() on
   guest memory while vCPUs are accessing said memory, e.g. to verify KVM
   and mmu_notifiers are working as intended.
 - Play nice with treewrite builds of unsupported architectures, e.g. arm
   (32-bit), as KVM selftests' Makefile doesn't do anything to ensure the
   target architecture is actually one KVM selftests supports.
 - Use the kernel's $(ARCH) definition instead of the target triple for arch
   specific directories, e.g. arm64 instead of aarch64, mainly so as not to
   be different from the rest of the kernel.
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions
