On Fri, 29 May 2009, Magnus Damm wrote: > > (And by the way, the _noirq ops don't run in atomic context. They run > > in process context with most interrupt deliveries disabled. It's not > > the same thing -- they are allowed to sleep.) > > Huh, so if they are allowed to sleep then clock events are still > running. And probably some clocksource as well. I guess that's why you > say "most" interrupts disabled instead of all. Sharing the timer IRQ > is not allowed then? Rafael can tell you. But notice I didn't say the interrupts were disabled -- I said that interrupt _delivery_ was disabled. In general the interrupts themselves _are_ enabled; the kernel fields them but then does not call the drivers' interrupt handler routines. (Except perhaps for IRQs which are explicitly marked as wakeup sources...) > I wonder if the PM code assumes that the clock event is a sys device? > We use platform drivers for clock events on SuperH... Ask Rafael. Alan Stern _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
