On Tue, 2007-08-14 at 07:36 +0200, Thomas Gleixner wrote:
> On Mon, 2007-08-13 at 19:26 -0400, Joe Korty wrote:
> > Retrigger_next_event() must be called with interrupts disabled.
> >
> > All internal (to hrtimer.c) uses of retrigger_next_event() are correct.
> > But the version exported to other
On Tue, 2007-08-14 at 07:36 +0200, Thomas Gleixner wrote:
On Mon, 2007-08-13 at 19:26 -0400, Joe Korty wrote:
Retrigger_next_event() must be called with interrupts disabled.
All internal (to hrtimer.c) uses of retrigger_next_event() are correct.
But the version exported to other files,
On Mon, 2007-08-13 at 19:26 -0400, Joe Korty wrote:
> Retrigger_next_event() must be called with interrupts disabled.
>
> All internal (to hrtimer.c) uses of retrigger_next_event() are correct.
> But the version exported to other files, hres_timers_resume(), does not
> do the IRQ blocking, nor
Retrigger_next_event() must be called with interrupts disabled.
All internal (to hrtimer.c) uses of retrigger_next_event() are correct.
But the version exported to other files, hres_timers_resume(), does not
do the IRQ blocking, nor does the (single) external caller of it.
Rather than require
Retrigger_next_event() must be called with interrupts disabled.
All internal (to hrtimer.c) uses of retrigger_next_event() are correct.
But the version exported to other files, hres_timers_resume(), does not
do the IRQ blocking, nor does the (single) external caller of it.
Rather than require
On Mon, 2007-08-13 at 19:26 -0400, Joe Korty wrote:
Retrigger_next_event() must be called with interrupts disabled.
All internal (to hrtimer.c) uses of retrigger_next_event() are correct.
But the version exported to other files, hres_timers_resume(), does not
do the IRQ blocking, nor does
6 matches
Mail list logo