From: Xiaoning Ding <dingxn@ymail.com>
To: Wes Felter <wesley@felter.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: a question about p4_clockmod module on Xeon quad core processors
Date: Thu, 29 Jan 2009 17:12:06 -0800 (PST) [thread overview]
Message-ID: <497399.1935.qm@web59909.mail.ac4.yahoo.com> (raw)
In-Reply-To: <498215C9.6090208@felter.org>
It works on my machine. Thanks for the help!
Xiaoning
--- On Thu, 1/29/09, Wes Felter <wesley@felter.org> wrote:
> From: Wes Felter <wesley@felter.org>
> Subject: Re: a question about p4_clockmod module on Xeon quad core processors
> To: dingxn@ymail.com
> Cc: linux-kernel@vger.kernel.org
> Date: Thursday, January 29, 2009, 8:47 PM
> This will give you an effective speed of 250 MHz:
>
> for cpu in 0 1 2 3; do
> cpufreq-set -c $cpu -g userspace
> cpufreq-set -c $cpu -u 2.0GHz
> wrmsr -p $cpu 0x19A 0x12
> done
>
> 0x19A is the IA32_CLOCK_MODULATION MSR and 0x12 is
> calculated from the Intel 64 and IA-32 Architectures
> Software Developer’s Manual section 13.5.3. Legal MSR
> values are 0x12 (12.5% duty cycle) - 0x1E (87.5%) or 0x00
> for 100%. I tested it on a quad-core Xeon and it works.
>
> This is somewhat reckless, so use it with caution.
>
> Wes Felter - wesley@felter.org
prev parent reply other threads:[~2009-01-30 1:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 20:17 a question about p4_clockmod module on Xeon quad core processors Xiaoning Ding
2009-01-27 21:23 ` Arjan van de Ven
2009-01-29 16:12 ` Xiaoning Ding
2009-01-28 21:02 ` Dave Jones
2009-01-29 2:06 ` Xiaoning Ding
2009-01-29 2:45 ` Dave Jones
2009-01-29 16:32 ` Xiaoning Ding
2009-01-29 17:08 ` Dave Jones
2009-01-29 12:27 ` Michael Tokarev
2009-01-29 17:24 ` Dave Jones
2009-01-29 19:40 ` Xiaoning Ding
2009-01-29 19:54 ` Dave Jones
2009-01-28 21:05 ` Wes Felter
2009-01-29 2:11 ` Xiaoning Ding
2009-01-29 20:47 ` Wes Felter
2009-01-30 1:12 ` Xiaoning Ding [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=497399.1935.qm@web59909.mail.ac4.yahoo.com \
--to=dingxn@ymail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wesley@felter.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