From: "Artem S. Tashkinov" <t.artem@lycos.com>
To: linux-kernel@vger.kernel.org
Cc: davej@redhat.com, cpufreq@vger.kernel.org
Subject: cpufreq userspace governor doesn't work for Intel Core 2 Gen 2 CPUs
Date: Sun, 25 Dec 2011 18:36:29 +0000 (GMT) [thread overview]
Message-ID: <388674780.142932.1324838189780.JavaMail.mail@webmail18> (raw)
In-Reply-To: 1982761334.142905.1324837801755.JavaMail.mail@webmail18
Hello,
On my Intel Core i5 CPU with acpi-cpufreq module loaded I do this
# echo 2000000 | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_setspeed
then
# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
2000000
2000000
2000000
2000000
so theoretically it should work.
However i7z (http://code.google.com/p/i7z/) shows that CPU frequency is freely floating
and turbo boost gets enabled as soon as I have any discernible load, in other words
userspace CPU frequency driver doesn't work at all and it doesn't really enforce the specified
CPU frequency.
Best wishes,
Artem
parent reply other threads:[~2011-12-25 18:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1982761334.142905.1324837801755.JavaMail.mail@webmail18>]
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=388674780.142932.1324838189780.JavaMail.mail@webmail18 \
--to=t.artem@lycos.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--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