On Tue, Feb 03, 2015 at 03:36:19PM -0500, Steven Rostedt wrote: > On Mon, 2 Feb 2015 19:02:29 -0200 > Marcelo Tosatti <mtosatti@xxxxxxxxxx> wrote: > > > I am worried about two things: > > > > 1) Something calling raise_softirq(TIMER_SOFTIRQ) and lack of > > Paul's d550e81dc0dd. > > > > The result is __run_timers checking all timer wheel "nodes" > > and updating base->timer_jiffies, latency is ruined. > > > > Even if one carefully made sure no timer is present. > > > > 2) Reliance on sched timer interrupt to raise timer softirq > > in case of pending irq work (your patch) AND no_hz_full. > > > > > Isolation is the *only* way to make that work. > > > > Fine. Please see item 1) above. > > > > So basically you are saying we just need: d550e81dc0dd ? For 1), the 4 patches he mentioned, please. For 2), it was just a hypothesis (perhaps fuelled by the fact the my test box crashes with nohz_full= and isolated cpus). -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
