From: Thomas Gleixner <tglx@linutronix.de>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: RE: bug seen with dynticks from CONFIG_HARDIRQS_SW_RESEND
Date: Fri, 18 May 2007 09:49:27 +0200 [thread overview]
Message-ID: <1179474567.12981.53.camel@chaos> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D913027429010259ED@dlee13.ent.ti.com>
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
next prev parent reply other threads:[~2007-05-18 7:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 23:20 Woodruff, Richard
2007-05-17 10:10 ` Thomas Gleixner
2007-05-17 20:14 ` Woodruff, Richard
2007-05-17 20:38 ` Thomas Gleixner
2007-05-17 22:24 ` Woodruff, Richard
2007-05-18 7:49 ` Thomas Gleixner [this message]
2008-04-18 15:43 ` Higer latency with dynamic tick (need for an io-ondemand govenor?) Woodruff, Richard
2008-04-19 3:45 ` [linux-pm] " David Brownell
2008-04-19 7:13 ` Thomas Gleixner
2008-04-19 22:49 ` david
2008-04-20 3:51 ` David Brownell
2008-04-20 6:19 ` Arjan van de Ven
2008-04-20 14:09 ` Woodruff, Richard
2008-04-20 12:41 ` Andi Kleen
2008-04-20 14:21 ` Woodruff, Richard
2008-04-20 14:26 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1179474567.12981.53.camel@chaos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=r-woodruff2@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome