On Fri, Mar 02, 2007 at 03:10:55PM +0100, Jean Delvare wrote:

quoted text
> I'm not familiar with APCI at all so I didn't know, but what you write
> here brings some hope. Would it be possible to parse all the DSDT code
> at boot time and deduce all the ports which ACPI would need to request
> to be safe? Or do we have to wait for the accesses to actually happen?

In theory I /think/ so, but it would probably end up being an 
overestimate of the coverage actually needed. Trapping at runtime is 
arguably more elegant?

quoted text
> Do we know in advance when we are going to SMM mode and back? If we do,
> I'd be happy with a mutex every interested driver could use to protect
> relevant parts of its code. SMBus master drivers for example could
> request that mutex during SMBus transactions. Of course we don't know
> if SMM will actually touch the SMBus, but better safe than sorry I
> guess. And SMM calls aren't happening so frequently, are they?

My understanding is that pretty much arbitrary hardware access can cause 
SMM transitions without OS notification, though this is getting outside 
the areas I know about.
-- 
Matthew Garrett | mjg59@srcf.ucam.org
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/