diff options
author | Sean Christopherson <seanjc@google.com> | 2025-05-22 18:17:56 -0700 |
---|---|---|
committer | Sean Christopherson <seanjc@google.com> | 2025-06-25 09:51:33 -0700 |
commit | bbc13ae593e0ea47357ff6e4740c533c16c2ae1e (patch) | |
tree | 237023a86c121d99253fc0708e7c151a22ab27ab /scripts/lib/kdoc/kdoc_parser.py | |
parent | ff845e6a84c8c2c717efa6caf4db2d51a05aa9fd (diff) |
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 <jmattson@google.com>
Link: https://lore.kernel.org/r/20250523011756.3243624-6-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions