diff options
| author | Jim Mattson <[email protected]> | 2021-06-04 10:26:06 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2021-06-17 13:09:31 -0400 |
| commit | 966eefb8965798478c2a6de3aa35ec180323792d (patch) | |
| tree | edca2b0535056e70c21acdc1cb91ab1c8faa4c2b /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | 0fe998b295a37234392072c23e22b8bba4774d0f (diff) | |
KVM: nVMX: Disable vmcs02 posted interrupts if vmcs12 PID isn't mappable
Don't allow posted interrupts to modify a stale posted interrupt
descriptor (including the initial value of 0).
Empirical tests on real hardware reveal that a posted interrupt
descriptor referencing an unbacked address has PCI bus error semantics
(reads as all 1's; writes are ignored). However, kvm can't distinguish
unbacked addresses from device-backed (MMIO) addresses, so it should
really ask userspace for an MMIO completion. That's overly
complicated, so just punt with KVM_INTERNAL_ERROR.
Don't return the error until the posted interrupt descriptor is
actually accessed. We don't want to break the existing kvm-unit-tests
that assume they can launch an L2 VM with a posted interrupt
descriptor that references MMIO space in L1.
Fixes: 6beb7bd52e48 ("kvm: nVMX: Refactor nested_get_vmcs12_pages()")
Signed-off-by: Jim Mattson <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions