On Tue, 1 Jun 2010, Rafael J. Wysocki wrote: > On Tuesday 01 June 2010, Neil Brown wrote: > > My freerunner has a single core so without CONFIG_PREEMPT it may be that > > there is no actual race-window - maybe the PRE_SUSPENDs will all run before a > > soft_irq thread has a chance to finish handling of the interrupt (my > > knowledge of these details is limits). But on a muilti-core device I think > > there would definitely be a race-window. > > Yes, there always will be a race window. The only thing we can do is to > narrow it, but we cannot really close it (at least not on a PC, but I'm not > really sure it can be closed at all). It can be closed, when the state transition from normal event delivery to wakeup mode is state safe, which it is on most platforms which are designed for the mobile space. Not so the current PC style x86 platforms, which are not relevant for the problem at hand at all. Really, that stuff is going either to gain sane properties or it's just going into the irrelevant realm. Any attempt to solve the current x86/ACPI/BIOS/mess is waste of time and is inevitably going to prevent progress. > If you really want _all_ events to be delivered timely, the only way to go is > to avoid using suspend (and use the idle framework for power management). Amen. tglx -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
