Today the RCU handling in Xen is affecting scheduling in several ways. It is raising sched softirqs without any real need and it requires tasklets for rcu_barrier(), which interacts badly with core scheduling.
This small series repairs those issues. Additionally some ASSERT()s are added for verification of sane rcu handling. In order to avoid those triggering right away the obvious violations are fixed. This includes making rcu locking functions type safe. Changes in V7: - new patch 1 - added some barriers in patch 1 Changes in V6: - added memory barrier in patch 1 - drop cpu_map_lock only at the end of rcu_barrier() - re-add prempt_disable() in patch 3 Changes in V5: - dropped already committed patches 1 and 4 - fixed race - rework blocking of rcu processing with held rcu locks Changes in V4: - patch 5: use barrier() Changes in V3: - type safe locking functions (functions instead of macros) - per-lock debug additions - new patches 4 and 6 - fixed races Changes in V2: - use get_cpu_maps() in rcu_barrier() handling - avoid recursion in rcu_barrier() handling - new patches 3 and 4 Juergen Gross (5): xen: introduce smp_mb__[after|before]_atomic() barriers xen/rcu: don't use stop_machine_run() for rcu_barrier() xen: don't process rcu callbacks when holding a rcu_read_lock() xen/rcu: add assertions to debug build xen/rcu: add per-lock counter in debug builds xen/common/rcupdate.c | 102 +++++++++++++++++++++++++++++++------------ xen/common/softirq.c | 14 +++++- xen/include/asm-arm/system.h | 3 ++ xen/include/asm-x86/system.h | 3 ++ xen/include/xen/rcupdate.h | 77 ++++++++++++++++++++++++++------ 5 files changed, 157 insertions(+), 42 deletions(-) -- 2.16.4