From: Dave Jones <davej@redhat.com>
To: matthias brill <matthias.brill@akamail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: banias with different (unusual?) model_name
Date: Mon, 23 Aug 2004 12:13:15 +0100 [thread overview]
Message-ID: <20040823111315.GA1589@redhat.com> (raw)
In-Reply-To: <20040821115316.GA2582@akamail.com>
On Sat, Aug 21, 2004 at 01:53:16PM +0200, matthias brill wrote:
> if i understand correctly, the type of the cpu can be determined by
> looking at the family, model and stepping -- assuming that these values
> are reported directly by the CPUID (0FA2) instruction.
download the source for x86info sometime, and look at the hoops
it jumps through to determine what cpu its running on. It isn't
just as simple as a few cpuid calls any more. These days there are
typically up to a half dozen factors that you need to look at to
discriminate between possibilities. One of these, is cpu speed.
Unfortunatly, as we could have booted off mains, and hence a lower
clock speed, we can't do any runtime calculation like we do with
bogomips/jiffies, so we have to resort to looking at the model name
supplied by the BIOS.
> the BIOS supplied model_name string in speedstep-centrino.c is parsed to
> get the clock cycle time of the cpu. is this actually supposed to be
> the "right" way (or worse: the only way) to get this information?
It's pretty much all we have that we can trust. If we could
do something else, I'd love to, as I distrust the abilities of
BIOS programmers as much as anyone else.
Dave
next prev parent reply other threads:[~2004-08-23 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 9:33 banias with different (unusual?) model_name matthias brill
2004-08-20 13:25 ` Alan Cox
2004-08-21 11:53 ` matthias brill
2004-08-23 11:13 ` Dave Jones [this message]
2004-08-21 2:19 ` Jeremy Fitzhardinge
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=20040823111315.GA1589@redhat.com \
--to=davej@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cpufreq@www.linux.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.brill@akamail.com \
/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