Date: Sat, 27 Mar 2010 16:35:36 +1100 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: Alexander Motin <mav@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Powerd and est / eist functionality Message-ID: <20100327153102.X30338@sola.nimnet.asn.au> In-Reply-To: <20100326091447.GA91547@icarus.home.lan> References: <5.2.1.1.2.20100324134153.032459d8@mail.sstec.com> <1269310984.00232724.1269300005@10.7.7.3> <1269310984.00232724.1269300005@10.7.7.3> <5.2.1.1.2.20100324134153.032459d8@mail.sstec.com> <5.2.1.1.2.20100325235505.031e8338@mail.sstec.com> <20100326091447.GA91547@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 26 Mar 2010, Jeremy Chadwick wrote:
[ leaving the MB monitoring stuff alone for your expert attention :-]
> > It jumped up in vcore a little there with powerd. C1E and C2E which
> > include P-states are what I am really after and I think that the
> > bios by itself provides those changes better than any other changes
> > in these settings.
>
> ...and this would fall under the est(4) subset driver for cpufreq(4).
Just checking, I know nothing about these so far, but are you suggesting
that John having C1E and C2E enabled in BIOS may be affecting ACPI/EST
detection, and that things may be different were these disabled?
If that's not what you meant, could you expand a little?
John: you may want to explore where this comes together in kern_cpu.c
where you'll see those cpufreq debugging messages you quoted. Some of
the more gritty documentation may be found browsing with something like:
% less /sys/{sys,kern,amd64/include}/*cpu*.[ch]
cheers, Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100327153102.X30338>