rcu,nohz,kvm: use RCU extended quiescent state when running KVM guest
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 12 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | rcu,nohz: add context_tracking_user_enter/exit wrapper functionsinclude/ kernel/ | +27 | 5 replies | |
| 2/6 | rcu,nohz: add state parameter to context_tracking_enter/exitinclude/ kernel/ | +12 | 0 replies | |
| 3/6 | nohz: add stub context_tracking_is_enabledinclude/ | +2 | 0 replies | |
| 4/6 | rcu,nohz: run vtime_user_enter/exit only when state == IN_USERkernel/ | +8 | 0 replies | |
| 5/6 | nohz,kvm: export context_tracking_user_enter/exitkernel/ | +2 | 0 replies | |
| 6/6 | kvm,rcu,nohz: use RCU extended quiescent state when running KVM guestinclude/ include/ include/ | +9 | 7 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH -v4 0/6] rcu,nohz,kvm: use RCU extended quiescent state when running KVM guest
When running a KVM guest on a system with NOHZ_FULL enabled, and the KVM guest running with idle=poll mode, we still get wakeups of the rcuos/N threads.
This problem has already been solved for user space by telling the RCU subsystem that the CPU is in an extended quiescent state while running user space code.
This patch series extends that code a little bit to make it usable to track KVM guest space, too.
I tested the code by booting a KVM guest with idle=poll, on a system with NOHZ_FULL enabled on most CPUs, and a VCPU thread bound to a CPU. In a 10 second interval, rcuos/N threads on other CPUs got woken up several times, while the rcuos thread on the CPU running the bound and alwasy running VCPU thread never got woken up once.
Thanks to Christian Borntraeger, Paul McKenney, Paulo Bonzini, Frederic Weisbecker, and Will Deacon for reviewing and improving earlier versions of this patch series.