On Fri, Jan 26, 2024, Vitaly Kuznetsov wrote: > Sean Christopherson <seanjc@xxxxxxxxxx> writes: > > > Get a reference to the target VM's address space in async_pf_execute() > > instead of gifting a reference from kvm_setup_async_pf(). Keeping the > > address space alive just to service an async #PF is counter-productive, > > i.e. if the process is exiting and all vCPUs are dead, then NOT doing > > get_user_pages_remote() and freeing the address space asap is > > desirable. > > It took me a while to realize why all vCPU fds are managed by the same > mm which did KVM_CREATE_VM as (AFAIU) fds can be passed around. Turns > out, we explicitly forbid this in kvm_vcpu_ioctl(): > > if (vcpu->kvm->mm != current->mm || vcpu->kvm->vm_dead) > return -EIO; > > so this indeed means that grabbing current->mm in kvm_setup_async_pf() > can be avoided. I'm not sure whether it's just me or a "all vCPUs are > quired to be managed by the same mm" comment somewhere would be helpful. It's definitely not just you. Documentation/virt/kvm/* could use thorough documentation of what all in KVM relies on vCPUs, and all meaningful ioctls(), to be executed in the same mm_struct (address space). Because that requirement is pervasive throughout KVM. E.g. sharing KVM page tables across vCPUs is safe iff all vCPUs are in the same address space, otherwise the hva=>pfn translations through the memslot would diverge, mmu_notifiers would be all kinds of broken, etc.
