Re: generic one-shot bug (was Re: sparc generic time / clockevents)

2007-02-25 Thread Thomas Gleixner
On Sat, 2007-02-24 at 21:13 -0800, David Miller wrote: > As I suspected, the one-shot code wasn't very well tested and I'd be > the one to debug this thing on sparc64 :-) > > When a timer exceeds the timer period, the one-shot handling code does > the following loop: > > for (;;) { >

Re: generic one-shot bug (was Re: sparc generic time / clockevents)

2007-02-25 Thread Thomas Gleixner
On Sat, 2007-02-24 at 21:13 -0800, David Miller wrote: As I suspected, the one-shot code wasn't very well tested and I'd be the one to debug this thing on sparc64 :-) When a timer exceeds the timer period, the one-shot handling code does the following loop: for (;;) {

generic one-shot bug (was Re: sparc generic time / clockevents)

2007-02-24 Thread David Miller
As I suspected, the one-shot code wasn't very well tested and I'd be the one to debug this thing on sparc64 :-) When a timer exceeds the timer period, the one-shot handling code does the following loop: for (;;) { ktime_t next = ktime_add(dev->next_event, tick_period);

generic one-shot bug (was Re: sparc generic time / clockevents)

2007-02-24 Thread David Miller
As I suspected, the one-shot code wasn't very well tested and I'd be the one to debug this thing on sparc64 :-) When a timer exceeds the timer period, the one-shot handling code does the following loop: for (;;) { ktime_t next = ktime_add(dev-next_event, tick_period);