Date: Sat, 01 Dec 2012 11:10:00 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= <dumbbell@FreeBSD.org> Cc: freebsd-acpi@FreeBSD.org Subject: Re: [rfc] bind curthread to target cpu for _CST change notification Message-ID: <50B9C968.70804@FreeBSD.org> In-Reply-To: <50B9C7B6.1040306@FreeBSD.org> References: <50AE3C66.2050207@FreeBSD.org> <1353872249.20189.3.camel@powernoodle> <50B77F4B.8070701@FreeBSD.org> <50B8951D.1000609@FreeBSD.org> <50B9C7B6.1040306@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50B9C968.70804>