From: Philip Lawatsch <philip@lawatsch.at>
To: Matteo Giordano <ilmalteo@gmail.com>, cpufreq@lists.linux.org.uk
Subject: Re: Make overclock possible with cpufreq
Date: Mon, 29 May 2006 11:48:05 +0200 [thread overview]
Message-ID: <447AC355.7070403@lawatsch.at> (raw)
In-Reply-To: <6d24915a0605281326j597faae7u49daaf78c962e2db@mail.gmail.com>
Matteo Giordano wrote:
> Hi,
> I just subscribed to the list to address this issue (I think it's an
> *issue*).
> I'm not a kernel hacker so I'm just guessing here, even if I searched
> and tried all the afternoon.
> It's not possible to use cpufreq with an overclocked CPU because the
> processor's frequencies are "hardcoded" somewhere (the BIOS or a PSB
> table?).
> So if I push my Athlon 64 3200+ to 2.4GHz the "performance" governor
> will always put it to 2GHz max, causing the overclock to be useless.
Note, I'm only a cpufreq user myself, so I might be wrong, but these are
my observations:
.) k8 powernow only changes the multiplier, but not the reference clock.
Thus if you overclock the reference clock and do not change anything
else you should be fine.
.) cpufreq _did_ (back in 2.6.15?) report the actual cpu frequencies in
/proc/cpuinfo, but this changed and now it reports the frequency it
thinks the cpu is running at.
One way to verify that the cpu is still overclocked is to simply look at
the bogomips value in /proc/cpuinfo or run some benchmarks.
In my case I've still got the (expected) higher bogomips value for 2.6
ghz even though cpufreq thinks that the cpu is at 2.2 ghz.
kind regards Philip
prev parent reply other threads:[~2006-05-29 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 20:26 Make overclock possible with cpufreq Matteo Giordano
2006-05-28 21:22 ` Dave Jones
2006-05-29 14:42 ` Bruno Ducrot
2006-05-29 9:48 ` Philip Lawatsch [this message]
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=447AC355.7070403@lawatsch.at \
--to=philip@lawatsch.at \
--cc=cpufreq@lists.linux.org.uk \
--cc=ilmalteo@gmail.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 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.