On Thu, Aug 23, 2012 at 12:46:37PM +0200, Thomas Gleixner wrote:
> On Thu, 23 Aug 2012, Sedat Dilek wrote:
>
> > Hi,
> >
> > this week I was seeing the below NOHZ messages in my logs especially
> > when suspending and resuming.
> >
> > Currently, I am using linux-next (next-20120823) on Ubuntu/precise
> > AMD64 with a Intel S(a)N(dy)B(ridge)-CPU.
> >
> > $ dmesg | grep -A1 -B1 -i nohz
> > [ 720.331819] Disabling non-boot CPUs ...
> > [ 720.332035] NOHZ: local_softirq_pending 200
> > [ 720.434312] smpboot: CPU 1 is now offline
> > [ 720.434825] NOHZ: local_softirq_pending 200
> > [ 720.538237] smpboot: CPU 2 is now offline
> > [ 720.538676] NOHZ: local_softirq_pending 200
> > [ 720.642162] smpboot: CPU 3 is now offline
> >
> > If I manually disable the cpuX... First I did not see NOHZ messages
> > but then there were some lines seen especially when cpuX went offline
> > (here: cpu1)
> >
> > # echo 0 >/sys/devices/system/cpu/cpu1/online
> >
> > [ dmeg ]
> > [ 2605.515771] smpboot: CPU 1 is now offline
> >
> > The same with cpu2 and cpu3.
Hmmm... RCU is actually relying on being able to prevent entry into idle
by raising softirq. This is needed for the aggressive energy-efficiency
CONFIG_RCU_FAST_NO_HZ feature of RCU. Therefore, I propose the patch
shown below.
Sedat, does this patch help?
Thanx, Paul
> > Jack Winter confirmed to see similiar NOHZ messages also on
> > v3.4.9-rt17 kernel (CPU: Core2Duo when no suspend performed):
> >
> > [15223.171585] NOHZ: local_softirq_pending 08
>
> That's a different issue. That's a pending networking softirq when we
> go idle. Unrelated to the RCU / hotplug issue you are observing.
>
> > So, the issue is seen on linux-next and -rt kernels.
> >
> > According to Thomas "softirq 0x200 is the RCU one" and he requested me
> > to address the issue to Paul on #linux-rt.
> >
> > Regards,
> > - Sedat -
time: RCU permitted to stop idle entry via softirq
RCU needs to be able to use softirq to stop idle entry in order to
be able to drain RCU callbacks from the current CPU, which in turn
enables faster entry into dyntick-idle mode, which in turn reduces power
consumption. This commit therefore silences the error message that is
sometimes produced when the going-idle CPU suddenly finds that it has
an RCU_SOFTIRQ to process.
Signed-off-by: Paul E. McKenney <paul.mckenney@xxxxxxxxxx>
diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
index c5f856a..c0359d2 100644
--- a/include/linux/interrupt.h
+++ b/include/linux/interrupt.h
@@ -430,6 +430,8 @@ enum
NR_SOFTIRQS
};
+const int softirq_stop_idle_mask = (~(1 << RCU_SOFTIRQ));
+
/* map softirq index to softirq name. update 'softirq_to_name' in
* kernel/softirq.c when adding a new softirq.
*/
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index 024540f..84932cf 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -436,7 +436,8 @@ static bool can_stop_idle_tick(int cpu, struct tick_sched *ts)
if (unlikely(local_softirq_pending() && cpu_online(cpu))) {
static int ratelimit;
- if (ratelimit < 10) {
+ if (ratelimit < 10 &&
+ (local_softirq_pending() & softirq_stop_idle_mask)) {
printk(KERN_ERR "NOHZ: local_softirq_pending %02x\n",
(unsigned int) local_softirq_pending());
ratelimit++;
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
