diff options
| author | Vitaly Kuznetsov <[email protected]> | 2021-06-09 17:09:10 +0200 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2021-06-17 13:09:55 -0400 |
| commit | bca66dbcd28a41c669921ff7ca066f71e6f3e72e (patch) | |
| tree | c4b9fdfbb711699cc01c3cf40a892de09920b5ca /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | c5ffd408cdc951ba153aea267d96d7cc62c6a97c (diff) | |
KVM: x86: Check for pending interrupts when APICv is getting disabled
When APICv is active, interrupt injection doesn't raise KVM_REQ_EVENT
request (see __apic_accept_irq()) as the required work is done by hardware.
In case KVM_REQ_APICV_UPDATE collides with such injection, the interrupt
may never get delivered.
Currently, the described situation is hardly possible: all
kvm_request_apicv_update() calls normally happen upon VM creation when
no interrupts are pending. We are, however, going to move unconditional
kvm_request_apicv_update() call from kvm_hv_activate_synic() to
synic_update_vector() and without this fix 'hyperv_connections' test from
kvm-unit-tests gets stuck on IPI delivery attempt right after configuring
a SynIC route which triggers APICv disablement.
Signed-off-by: Vitaly Kuznetsov <[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