diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2025-02-26 13:23:29 -0500 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2025-03-20 13:13:00 -0400 |
commit | 361da275e5ce98bbab5f6990d02eb9709742d703 (patch) | |
tree | 4c3d778f94b19cfa76eed868b60dedd6bf57a1c0 /Documentation/RCU/stallwarn.rst | |
parent | 0afd104fb352f2133bbefcaf9761d28bd9dbc961 (diff) | |
parent | b2aba529bf77ebdc1a1841b884ff841c1d21f6af (diff) |
Merge branch 'kvm-nvmx-and-vm-teardown' into HEAD
The immediate issue being fixed here is a nVMX bug where KVM fails to
detect that, after nested VM-Exit, L1 has a pending IRQ (or NMI).
However, checking for a pending interrupt accesses the legacy PIC, and
x86's kvm_arch_destroy_vm() currently frees the PIC before destroying
vCPUs, i.e. checking for IRQs during the forced nested VM-Exit results
in a NULL pointer deref; that's a prerequisite for the nVMX fix.
The remaining patches attempt to bring a bit of sanity to x86's VM
teardown code, which has accumulated a lot of cruft over the years. E.g.
KVM currently unloads each vCPU's MMUs in a separate operation from
destroying vCPUs, all because when guest SMP support was added, KVM had a
kludgy MMU teardown flow that broke when a VM had more than one 1 vCPU.
And that oddity lived on, for 18 years...
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'Documentation/RCU/stallwarn.rst')
0 files changed, 0 insertions, 0 deletions