diff options
author | Leonardo Bras <leobras@redhat.com> | 2024-05-11 04:05:56 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-09-04 16:44:42 +0200 |
commit | 593377036e50de89132bc1222800174fde0780ec (patch) | |
tree | 84cfe3462a8af2675378fe39427c479587cded1f /arch/x86/kvm/Kconfig | |
parent | KVM: x86: Only advertise KVM_CAP_READONLY_MEM when supported by VM (diff) | |
download | linux-593377036e50de89132bc1222800174fde0780ec.tar.xz linux-593377036e50de89132bc1222800174fde0780ec.zip |
kvm: Note an RCU quiescent state on guest exit
As of today, KVM notes a quiescent state only in guest entry, which is good
as it avoids the guest being interrupted for current RCU operations.
While the guest vcpu runs, it can be interrupted by a timer IRQ that will
check for any RCU operations waiting for this CPU. In case there are any of
such, it invokes rcu_core() in order to sched-out the current thread and
note a quiescent state.
This occasional schedule work will introduce tens of microsseconds of
latency, which is really bad for vcpus running latency-sensitive
applications, such as real-time workloads.
So, note a quiescent state in guest exit, so the interrupted guests is able
to deal with any pending RCU operations before being required to invoke
rcu_core(), and thus avoid the overhead of related scheduler work.
Signed-off-by: Leonardo Bras <leobras@redhat.com>
Acked-by: Paul E. McKenney <paulmck@kernel.org>
Acked-by: Sean Christopherson <seanjc@google.com>
Message-ID: <20240511020557.1198200-1-leobras@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kvm/Kconfig')
0 files changed, 0 insertions, 0 deletions