diff options
| author | Sean Christopherson <[email protected]> | 2025-05-23 01:17:56 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2025-06-25 16:51:33 +0000 |
| commit | bbc13ae593e0ea47357ff6e4740c533c16c2ae1e (patch) | |
| tree | 237023a86c121d99253fc0708e7c151a22ab27ab /tools/testing/selftests/kvm/lib/kvm_util.c | |
| parent | Revert "kvm: detect assigned device via irqbypass manager" (diff) | |
| download | kernel-bbc13ae593e0ea47357ff6e4740c533c16c2ae1e.tar.gz kernel-bbc13ae593e0ea47357ff6e4740c533c16c2ae1e.zip | |
VFIO: KVM: x86: Drop kvm_arch_{start,end}_assignment()
Drop kvm_arch_{start,end}_assignment() and all associated code now that
KVM x86 no longer consumes assigned_device_count. Tracking whether or not
a VFIO-assigned device is formally associated with a VM is fundamentally
flawed, as such an association is optional for general usage, i.e. is prone
to false negatives. E.g. prior to commit 2edd9cb79fb3 ("kvm: detect
assigned device via irqbypass manager"), device passthrough via VFIO would
fail to enable IRQ bypass if userspace omitted the formal VFIO<=>KVM
binding.
And device drivers that *need* the VFIO<=>KVM connection, e.g. KVM-GT,
shouldn't be relying on generic x86 tracking infrastructure.
Cc: Jim Mattson <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/testing/selftests/kvm/lib/kvm_util.c')
0 files changed, 0 insertions, 0 deletions