[lm-sensors] Could the k8temp driver be interfering with ACPI?
khali at linux-fr.org
Fri Mar 2 15:10:55 CET 2007
On Fri, 2 Mar 2007 11:47:47 +0000, Matthew Garrett wrote:
> 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.
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?
> Of course, this ignores the case where the DSDT just traps into SMM
> code. That one is clearly unsolvable.
Yeah, SMM is an even more complex problem :(
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?
More information about the lm-sensors