diff options
| author |   Sean Christopherson <seanjc@google.com> | 2025-06-11 15:45:56 -0700 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2025-06-23 09:50:46 -0700 |
| commit | 77e1b8332d1d7aa786f7515e9bd4055def6a1e06 (patch) | |
| tree | 1296fa23ff28f561dd85603ab46fce84a01173d4 /scripts/basic/git:/ssh:/git@git.zx2c4.com | |
| parent | KVM: SVM: WARN if ir_list is non-empty at vCPU free (diff) | |
| download | wireguard-linux-77e1b8332d1d7aa786f7515e9bd4055def6a1e06.tar.xz wireguard-linux-77e1b8332d1d7aa786f7515e9bd4055def6a1e06.zip | |
KVM: x86: Decouple device assignment from IRQ bypass
Use a dedicated counter to track the number of IRQs that can utilize IRQ
bypass instead of piggybacking the assigned device count. As evidenced by
commit 2edd9cb79fb3 ("kvm: detect assigned device via irqbypass manager"),
it's possible for a device to be able to post IRQs to a vCPU without said
device being assigned to a VM.
Leave the calls to kvm_arch_{start,end}_assignment() alone for the moment
to avoid regressing the MMIO stale data mitigation. KVM is abusing the
assigned device count when applying mmio_stale_data_clear, and it's not at
all clear if vDPA devices rely on this behavior. This will hopefully be
cleaned up in the future, as the number of assigned devices is a terrible
heuristic for detecting if a VM has access to host MMIO.
Link: https://lore.kernel.org/r/20250611224604.313496-55-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/basic/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions