On Fri 2007-03-02 11:47:47, Matthew Garrett wrote: > On Fri, Mar 02, 2007 at 12:40:23PM +0100, Pavel Machek wrote: > > > Whitelist seems like a way to go :(. > > The DSDT code clearly can't touch the hardware itself - hardware access > is carried out by the kernel. If we can identify cases where ACPI reads > and writes would touch resources claimed by other drivers, that would be > a good starting point for working out what's going on. > > Of course, this ignores the case where the DSDT just traps into SMM > code. That one is clearly unsolvable. We can't solve SMM stuff. (Whitelist needed :-). Actually for the acpi stuff... we might wrap ACPI interpretter with a semaphore that needs to be taken before starting any AML code. Then just make sure sensors take same semaphore? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
