On Thu, 7 Jun 2007 16:48:01 +0100, Ralf Baechle <ralf@xxxxxxxxxxxxxx> wrote: > But even if so, the basic solution is the same - just ignore the interrupt > whenever it happens to be triggered. Or if it isn't shared with an > active performance counter interrupt, you could even disable_irq() it. Using disable_irq() on the counter/compare interrupt might make the WAIT instruction really not wait on some chips. It is implementation dependent wheather an assertion of masked interrupt break the WAIT instruction or not. Busy looping in cpu_idle() would not preferred, but I'm not sure this is really a problem yet. Maybe I should have closer look at dyntick. --- Atsushi Nemoto
