KVM: x86: Decouple device assignment from IRQ bypass

Browse source

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 2edd9cb79f ("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>

...

This commit is contained in:

Sean Christopherson 2025-06-11 15:45:56 -07:00

parent 99836eb9c5

commit 77e1b8332d

7 changed files with 25 additions and 13 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

arch/x86/include/asm/kvm-x86-ops.h

View file

4

arch/x86/include/asm/kvm_host.h

View file

9

arch/x86/kvm/irq.c

View file

2

arch/x86/kvm/vmx/main.c

View file

16

arch/x86/kvm/vmx/posted_intr.c

View file

2

arch/x86/kvm/vmx/posted_intr.h

View file

3

arch/x86/kvm/x86.c

View file