Vitaly Kuznetsov f09db4e4d1 KVM: async_pf: Cleanup kvm_setup_async_pf() ... BugLink: https://bugs.launchpad.net/bugs/2067865 commit 7863e346e1 upstream. schedule_work() returns 'false' only when the work is already on the queue and this can't happen as kvm_setup_async_pf() always allocates a new one. Also, to avoid potential race, it makes sense to to schedule_work() at the very end after we've added it to the queue. While on it, do some minor cleanup. gfn_to_pfn_async() mentioned in a comment does not currently exist and, moreover, we can check kvm_is_error_hva() at the very beginning, before we try to allocate work so 'retry_sync' label can go away completely. Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> Message-Id: <20200610175532.779793-1-vkuznets@redhat.com> Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Portia Stephens <portia.stephens@canonical.com> Signed-off-by: Stefan Bader <stefan.bader@canonical.com>		2024-06-07 15:01:45 +02:00
..
arm	KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler	2024-04-26 10:54:04 +02:00
Kconfig	…
async_pf.c	KVM: async_pf: Cleanup kvm_setup_async_pf()	2024-06-07 15:01:45 +02:00
async_pf.h	…
coalesced_mmio.c	KVM: Destroy target device if coalesced MMIO unregistration fails	2023-05-12 17:15:09 +02:00
coalesced_mmio.h	…
eventfd.c	…
irqchip.c	…
kvm_main.c	KVM: Add infrastructure and macro to mark VM as bugged	2022-10-17 15:01:31 +02:00
vfio.c	…
vfio.h	…