On Mon, Apr 22, 2024, Oliver Upton wrote: > A subsequent change to KVM/arm64 will necessitate walking the device > list outside of the kvm->lock. Prepare by converting to an rculist. This > has zero effect on the VM destruction path, as it is expected every > reader is backed by a reference on the kvm struct. > > On the other hand, ensure a given device is completely destroyed before > dropping the kvm->lock in the release() path, as certain devices expect > to be a singleton (e.g. the vfio-kvm device). > > Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx> > Cc: Sean Christopherson <seanjc@xxxxxxxxxx> > Signed-off-by: Oliver Upton <oliver.upton@xxxxxxxxx> > --- Reviewed-by: Sean Christopherson <seanjc@xxxxxxxxxx>
