[rfc] bind curthread to target cpu for _CST change notification

Andriy Gapon avg at FreeBSD.org
Sat Dec 1 09:10:04 UTC 2012


on 01/12/2012 11:02 Jean-Sébastien Pédron said the following:
> On 30.11.2012 12:14, Andriy Gapon wrote:
>> Here is my WIP: http://people.freebsd.org/~avg/acpi_cpu_notify.2.diff
> 
> Hi Andriy!
> 
> I tried your last patch and it fixed a page fault I had since r243404 (I 
> couldn't investigate the problem before this week-end).
> 
> This page fault corresponds to the point #2 of your patch ("avoid race 
> acpi_cpu_cx_cst and acpi_cpu_idle"). In my case, acpi_cpu_cx_cst is 
> triggered every 10 seconds (I don't know if it's expected). This frees 
> cx_ptr->p_lvlx each time (new in r243404), and concurrently, 
> CPU_GET_REG(cx_next->p_lvlx, 1) causes the page fault in acpi_cpu_idle().

Thank you for testing!  I will commit this patch soon.

> By the way, should _CST appear in a dump from acpidump(8)?

Yes, it depends... :-)
_CST could be defined in a dynamically loadable region.  If you do not see
_CST in the DSDT but see Load() calls, then that's the most likely explanation.

-- 
Andriy Gapon


More information about the freebsd-acpi mailing list