KVM: X86: Bail out of direct yield in case of under-committed scenarios
authorWanpeng Li <wanpengli@tencent.com>
Tue, 18 May 2021 12:00:32 +0000 (05:00 -0700)
committerPaolo Bonzini <pbonzini@redhat.com>
Thu, 27 May 2021 11:45:52 +0000 (07:45 -0400)
commit72b268a8e9307a1757f61af080e990b5baa11d2a
tree3582e649e3f5d8da5f0fc99955a90407f903d609
parent6bd5b743686243dae7351d5dcceeb7f171201bb4
KVM: X86: Bail out of direct yield in case of under-committed scenarios

In case of under-committed scenarios, vCPUs can be scheduled easily;
kvm_vcpu_yield_to adds extra overhead, and it is also common to see
when vcpu->ready is true but yield later failing due to p->state is
TASK_RUNNING.

Let's bail out in such scenarios by checking the length of current cpu
runqueue, which can be treated as a hint of under-committed instead of
guarantee of accuracy. 30%+ of directed-yield attempts can now avoid
the expensive lookups in kvm_sched_yield() in an under-committed scenario.

Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
Message-Id: <1621339235-11131-2-git-send-email-wanpengli@tencent.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
arch/x86/kvm/x86.c