On Tue, Aug 07, 2007 at 02:26:16PM -0700, Ken Chen wrote: > I'm horrified to see the same code coming back: doing interrupt > enable/disable in the most inner while loop. Disable interrupt is > just crude, but I suppose that's the only way to resolve the race > condition? Looking at other arch like x86_64, it is also doing the > same thing. If anyone can suggest a better alternative to fix this race condition, I'd certainly consider it. I suppose one alternative might be to move the local_irq_enable() down into the default_idle loop so that we don't have to enable and disable irq's the first time through if pal_halt will be called. - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|