From: Robert Hancock <hancockr@shaw.ca>
To: Brian Morrison <bdm@fenrir.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel Core2Duo mobile - how does the VID get set?
Date: Tue, 19 Feb 2008 17:52:54 -0600 [thread overview]
Message-ID: <47BB6BD6.1090105@shaw.ca> (raw)
In-Reply-To: <fa.2QH6xosNob5B2/8HmS0yYeHCvG4@ifi.uio.no>
Brian Morrison wrote:
> Pallipadi, Venkatesh 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
>>
>> Yes. The freq and voltage supported comes from the platform BIOS. BIOS
>> exports this in an ACPI table which is handled by acpi-cpufreq driver in
>> Linux kernel.
>>
>
> OK, thanks for that.
>
>>
>>> b) whether there is an interface in /proc or /sys where one can find
>>> out what is set and modify it?
>>
>> There is no way of modifying and using new VIDs etc in Linux kernel
>> (other than exporting your own DSDT and hacking the related code).
>
> Is there a way of viewing the ACPI table contents relating to the VIDs
> and FIDs?
Viewing the decompiled ACPI DSDT may provide some hints, however the
kernel itself knows nothing about VID/FID settings for acpi-cpufreq,
basically the kernel writes to magic ACPI registers and the BIOS or
hardware take over to do what's required..
next parent reply other threads:[~2008-02-19 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
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=47BB6BD6.1090105@shaw.ca \
--to=hancockr@shaw.ca \
--cc=bdm@fenrir.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox