diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2024-05-12 10:18:44 +0300 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-05-12 10:18:44 +0300 |
commit | 7d41e24da29a83acc52a78a68aa515dd76e41cc1 (patch) | |
tree | 4ab35b9e1c69ff5b454844a0df16ee483ffc1f2d /tools/testing/selftests/kvm/arch_timer.c | |
parent | 5a1c72e07e830dda424f2929332a1435c9736da3 (diff) | |
parent | 51937f2aae186e335175dde78279aaf0cb5e72ae (diff) | |
download | linux-7d41e24da29a83acc52a78a68aa515dd76e41cc1.tar.xz |
Merge tag 'kvm-x86-misc-6.10' of https://github.com/kvm-x86/linux into HEAD
KVM x86 misc changes for 6.10:
- Advertise the max mappable GPA in the "guest MAXPHYADDR" CPUID field, which
is unused by hardware, so that KVM can communicate its inability to map GPAs
that set bits 51:48 due to lack of 5-level paging. Guest firmware is
expected to use the information to safely remap BARs in the uppermost GPA
space, i.e to avoid placing a BAR at a legal, but unmappable, GPA.
- Use vfree() instead of kvfree() for allocations that always use vcalloc()
or __vcalloc().
- Don't completely ignore same-value writes to immutable feature MSRs, as
doing so results in KVM failing to reject accesses to MSR that aren't
supposed to exist given the vCPU model and/or KVM configuration.
- Don't mark APICv as being inhibited due to ABSENT if APICv is disabled
KVM-wide to avoid confusing debuggers (KVM will never bother clearing the
ABSENT inhibit, even if userspace enables in-kernel local APIC).
Diffstat (limited to 'tools/testing/selftests/kvm/arch_timer.c')
0 files changed, 0 insertions, 0 deletions