Subject: RE: bug seen with dynticks from CONFIG_HARDIRQS_SW_RESEND
From: Thomas Gleixner <tglx@linutronix.de>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D913027429010259ED@dlee13.ent.ti.com>
References: <3B6D69C3A9EBCA4BA5DA60D913027429010253CD@dlee13.ent.ti.com>
	 <1179396659.3764.40.camel@chaos>
	 <3B6D69C3A9EBCA4BA5DA60D913027429010258E8@dlee13.ent.ti.com>
	 <1179434296.12981.14.camel@chaos>
	 <3B6D69C3A9EBCA4BA5DA60D913027429010259ED@dlee13.ent.ti.com>
Content-Type: text/plain
Date: Fri, 18 May 2007 09:49:27 +0200
Message-Id: <1179474567.12981.53.camel@chaos>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1073
Lines: 30

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/