Re: 'global' rq->clock

[Ingo Molnar]

* David Miller <davem@xxxxxxxxxxxxx> wrote:

> From: Ingo Molnar <mingo@xxxxxxx>
> Date: Sat, 3 May 2008 12:10:16 +0200
> 
> > ( although please note that the growing generalization that goes on
> >   _did_ find a subtle nohz problem on sparc64 early in the merge 
> >   window, so it's not like these changes are totally useless to you. 
> >   )
> 
> Note that this bug theoretically exists on every platform, even x86, 
> and only sparc64 is fixed at the moment by adding the 
> irq_{entry,exit}() guards around all of it's IPI handlers.
> 
> Just a reminder.

yeah, indeed - it's masked on x86 by the suckiness of most clockevents 
hw timers. We dont get unlimited sleep time like sparc64 does :-/

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