lkml.org 
[lkml]   [2007]   [May]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: bug seen with dynticks from CONFIG_HARDIRQS_SW_RESEND
From
Date
On Thu, 2007-05-17 at 17:24 -0500, Woodruff, Richard wrote:
> > This is the original ARM dyntick stuff, right ?
>
> Yes this is a version is not using clocksource.
>
> > The dyntick support on your architecture is broken. Why does it fiddle
> > with the timer, when the system is not idle ?
>
> I can't yet run the test sequence on the latest kernel so I'll have to
> wait to experiment. A brief look at the new code seems to show a
> similar path but I need to actually run though it to understand better.
>
>
> On the irq_resend() path handle_dynamic_tick() is still called as
> before.

No. NOHZ makes handle_dynamic_tick() a NOP. handle_dynamic_tick()
depends on CONFIG_NO_IDLE_HZ, which is not used when NOHZ is active.

The problem could only arise, when something would disable/enable the
timer interrupt.

tglx


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-05-18 09:47    [W:0.120 / U:0.464 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site