Date: Fri, 24 Aug 2007 18:31:05 -0400 From: "Constantine A. Murenin" <cnst@FreeBSD.org> To: "Nate Lawson" <nate@root.org> Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>, src-committers@freebsd.org, "Constantine A. Murenin" <cnst@freebsd.org>, cvs-all@freebsd.org, cvs-src@freebsd.org Subject: Re: cvs commit: src/sys/dev/coretemp coretemp.c Message-ID: <f34ca13c0708241531v2994fe35x442318ec3fe75872@mail.gmail.com> In-Reply-To: <46CDA669.8080601@root.org> References: <200708231053.l7NAr3Pc088160@repoman.freebsd.org> <86zm0izfhf.fsf@ds4.des.no> <46CDA669.8080601@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23/08/07, Nate Lawson <nate@root.org> wrote: > Dag-Erling Sm=F8rgrav wrote: > > Dag-Erling Smorgrav <des@FreeBSD.org> writes: > >> Log: > >> Style nits + more reliable Tj(max) detection + improved reporting of > >> critical temperature + sched_unbind() after rdmsr + initialize sc_de= v. > > > > I should note that the driver currently only checks for (and reports) a > > critical temperature when you read the sysctl; if you want to use devd > > to react to a critical temperature, you need to set up a cron job to > > poll dev.cpu.N.temperature. Hopefully, a future version of the driver > > will install an interrupt handler and activate the temperature threshol= d > > interrupts. > > > > DES > > You could also create a polling thread that runs every 10 seconds. We > have that for acpi_thermal currently. Actually, this is what coretemp(4) does in my cnst-sensors p4 branch, using a sensor_task, people are welcome to test it. ;) C.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f34ca13c0708241531v2994fe35x442318ec3fe75872>