From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
oliver@hartkopp.net
Subject: Re: [RFC PATCH] hrtimer: removing all ur callback modes
Date: Mon, 08 Dec 2008 17:13:02 +0100 [thread overview]
Message-ID: <1228752782.6939.2.camel@twins> (raw)
In-Reply-To: <1228385830.5092.43.camel@twins>
On Thu, 2008-12-04 at 11:17 +0100, Peter Zijlstra wrote:
> On Tue, 2008-11-25 at 12:43 +0100, Peter Zijlstra wrote:
> > Hi,
> >
> > This is an attempt at removing some of the hrtimer complexity by
> > reducing the number of callback modes to 1.
> >
> > This means that all hrtimer callback functions will be ran from HARD-irq
> > context.
> >
> > I went through all the 30 odd hrtimer callback functions in the kernel
> > and saw only one that I'm not quite sure of, which is the one in
> > net/can/bcm.c - hence I'm CC-ing the folks responsible for that code.
> >
> > Furthermore, the hrtimer core now calls callbacks directly with IRQs
> > disabled in case you try to enqueue an expired timer. If this timer is a
> > periodic timer (which should use hrtimer_forward() to advance its time)
> > then it might be possible to end up in an inf. recursive loop due to the
> > fact that hrtimer_forward() doesn't round up to the next timer
> > granularity, and therefore keeps on calling the callback - obviously
> > this needs a fix.
> >
> > Aside from that, this seems to compile and actually boot on my dual core
> > test box - although I'm sure there are some bugs in, me not hitting any
> > makes me certain :-)
> >
> > Not-Quite-Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
>
> Ingo, this addition fixes the hotplug issue on my machine
And because we're all human...
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
kernel/hrtimer.c | 5 +----
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index b09c7a2..e14af46 100644
--- a/kernel/hrtimer.c
+++ b/kernel/hrtimer.c
@@ -1571,7 +1571,7 @@ static void tickle_timers(void *arg)
static int __cpuinit hrtimer_cpu_notify(struct notifier_block *self,
unsigned long action, void *hcpu)
{
- int dcpu = -1, scpu = (long)hcpu;
+ int dcpu, scpu = (long)hcpu;
switch (action) {
@@ -1585,9 +1585,6 @@ static int __cpuinit hrtimer_cpu_notify(struct notifier_block *self,
case CPU_DEAD_FROZEN:
clockevents_notify(CLOCK_EVT_NOTIFY_CPU_DEAD, &scpu);
dcpu = migrate_hrtimers(scpu);
- break;
-
- case CPU_POST_DEAD:
if (dcpu == -1)
break;
next prev parent reply other threads:[~2008-12-08 16:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 11:43 [RFC PATCH] hrtimer: removing all ur callback modes Peter Zijlstra
2008-11-25 14:46 ` Ingo Molnar
2008-11-25 15:03 ` Ingo Molnar
2008-12-04 10:17 ` Peter Zijlstra
2008-12-04 10:33 ` Ingo Molnar
2008-12-07 11:22 ` Oliver Hartkopp
2008-12-07 12:59 ` Oliver Hartkopp
2008-12-08 10:15 ` Peter Zijlstra
2008-12-08 11:00 ` Oliver Hartkopp
2008-12-08 15:25 ` Linus Torvalds
2008-12-09 13:32 ` Takashi Iwai
2008-12-09 8:07 ` Oliver Hartkopp
2008-12-09 8:12 ` Peter Zijlstra
2008-12-09 10:59 ` Ingo Molnar
2008-12-30 22:46 ` Oliver Hartkopp
2008-12-31 8:32 ` Oliver Hartkopp
2008-12-08 16:13 ` Peter Zijlstra [this message]
2008-12-08 16:15 ` Peter Zijlstra
2008-12-08 16:18 ` Ingo Molnar
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=1228752782.6939.2.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oliver@hartkopp.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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