lkml.org 
[lkml]   [2006]   [Feb]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: + fix-next_timer_interrupt-for-hrtimer.patch added to -mm tree
* Thomas Gleixner <tglx@linutronix.de> [060228 01:03]:
> On Mon, 2006-02-27 at 19:29 -0800, Tony Lindgren wrote:
> > I've changed ARM xtime_lock to read lock, but now there's a slight
> > chance that an interrupt adds a timer after next_timer_interrupt() is
> > called and before timer is reprogrammed. I believe s390 also has this
> > problem.
>
> This needs a more generalized solution later, but I picked up your ARM
> change and simplified the hrtimer related bits.

Cool, after a quick test seems to work OK here. Any ideas how to fix the
locking problem above?

Maybe one option would be to just reprogram the hardware timer when a
new hrtimer is added. That would then allow subjiffie timers too.

Regards,

Tony
-
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: 2006-02-28 10:53    [W:0.150 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site