From: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
To: linux-kernel@vger.kernel.org
Subject: CPUFreq ability to overclock
Date: Thu, 22 Jun 2006 21:38:08 +0000 [thread overview]
Message-ID: <449B0DC0.8070203@aladin.ro> (raw)
*This message was transferred with a trial version of CommuniGate(r) Pro*
I'm thinking to implement a way to have CPUFreq's maximum FSB increased
to allow overclocking. Having that done, it should make sense to have a
governor (userspace maybe, with a 3rd-party tool) thermal-throttle the
CPU. There is one slight problem: can we control Vcore from within the
kernel, on-the-fly, without rebooting? I've seen a comment about scaling
voltages in cpufreq.c, but it seems there is no actual support for that.
My idea is to make cpufreq_policy.max (same for cpufreq_cpuinfo's
member) a soft limit (to prevent unwanted overclocking from usual
governors) and have another member hold the hard limit. Chipset drivers
should calculate the hard limit based on installed processor or
boot-time FSB.
I'm looking forward to comments and suggestions.
next reply other threads:[~2006-06-22 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 21:38 Eduard-Gabriel Munteanu [this message]
2006-06-22 18:47 ` CPUFreq ability to overclock 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=449B0DC0.8070203@aladin.ro \
--to=maxdamage@aladin.ro \
--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 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.