From: Wes Felter <wesley@felter.org>
To: Brian Morrison <bdm@fenrir.org.uk>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Intel Core2Duo mobile - how does the VID get set?
Date: Tue, 19 Feb 2008 13:12:29 -0600 [thread overview]
Message-ID: <47BB2A1D.1090306@felter.org> (raw)
In-Reply-To: <47BAC961.6030808@fenrir.org.uk>
Brian Morrison wrote:
> After a fair bit of Googling and reading around, I'm none the wiser
> about exactly how Linux 2.6.x sets the processor VID (or for that matter
> how it decides the FID settings) when using the ondemand governor and
> cpufreq stuff.
>
> Can anyone tell me a) whether this is obtained from the BIOS, something
> in the MSR of the processor or elsewhere and b) whether there is an
> interface in /proc or /sys where one can find out what is set and modify
> it?
There is an ACPI table created by the BIOS that lists all the P-states;
a P-state is a <frequency, opaque value> tuple where the opaque value
contains the FID and VID but Intel pretends it is magic. The
acpi-cpufreq driver reads this table and uses it to change states by
writing the opaque value into the appropriate MSR.
The Intel 64 and IA-32 Architectures Software Developer’s Manual, Volume
3A, chapter 13 describes the hardware (vaguely).
If you want to see what is going on under the hood, try Linux-PHC:
http://phc.athousandnights.de/
(Setting followup to cpufreq list.)
Wes Felter - wesley@felter.org
next prev parent reply other threads:[~2008-02-19 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 12:19 Intel Core2Duo mobile - how does the VID get set? Brian Morrison
[not found] ` <924EFEDD5F540B4284297C4DC59F3DEE90C8BD@orsmsx423.amr.corp.intel.com>
2008-02-19 18:33 ` Brian Morrison
2008-02-19 19:12 ` Wes Felter [this message]
[not found] <fa.PElYyuLIylS1JDURm06DXLz2hAs@ifi.uio.no>
[not found] ` <fa.pELF6tZ3LC4Qymp4Nyy0opWOQCE@ifi.uio.no>
[not found] ` <fa.2QH6xosNob5B2/8HmS0yYeHCvG4@ifi.uio.no>
2008-02-19 23:52 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47BB2A1D.1090306@felter.org \
--to=wesley@felter.org \
--cc=bdm@fenrir.org.uk \
--cc=cpufreq@lists.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.