Paolo Bonzini 7495e22bb1 KVM: Move running VCPU from ARM to common code ... For ring-based dirty log tracking, it will be more efficient to account writes during schedule-out or schedule-in to the currently running VCPU. We would like to do it even if the write doesn't use the current VCPU's address space, as is the case for cached writes (see commit 4e335d9e7d, "Revert "KVM: Support vCPU-based gfn->hva cache"", 2017-05-02). Therefore, add a mechanism to track the currently-loaded kvm_vcpu struct. There is already something similar in KVM/ARM; one important difference is that kvm_arch_vcpu_{load,put} have two callers in virt/kvm/kvm_main.c: we have to update both the architecture-independent vcpu_{load,put} and the preempt notifiers. Another change made in the process is to allow using kvm_get_running_vcpu() in preemptible code. This is allowed because preempt notifiers ensure that the value does not change even after the VCPU thread is migrated. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Peter Xu <peterx@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2020-01-27 19:59:54 +01:00
..
asm	KVM: Move running VCPU from ARM to common code	2020-01-27 19:59:54 +01:00
debug	Renesas ARM SoC updates for v5.4	2019-09-03 23:12:58 +02:00
uapi/asm	KVM: arm/arm64: Allow user injection of external data aborts	2019-10-21 18:59:51 +01:00