From: Tomasz Chmielewski <mangoo@wpkg.org>
To: trenn@suse.de
Cc: Martin.Leisner@xerox.com, cpufreq@lists.linux.org.uk
Subject: Re: Overall picture of cpufreq..
Date: Mon, 14 Jan 2008 11:59:35 +0100 [thread overview]
Message-ID: <478B4097.8010401@wpkg.org> (raw)
In-Reply-To: <1200306768.23376.332.camel@queen.suse.de>
Thomas Renninger schrieb:
(...)
>>> could it be that you are using
>>> p4-clockmode driver which is doing throttling, not frequency scaling,
>>> better try with acpi-cpufreq then.
>> Indeed, I am using p4-clockmod.
> Sorry, but your bug report is invalid then.
> p4-clockmod is using throttling (means the CPU ignores cycles/ticks) and
> not CPU frequency/voltage reduction.
> There is another interface for that:
> /proc/acpi/processor/throttling
Umm, do I need to build/insert some additional modules here?
# cat /proc/acpi/processor/CPU0/throttling
<not supported>
(...)
>> acpi-cpufreq doesn't work for me on that machine (p4-clockmod not loaded
>> when I try to insert acpi-cpufreq):
>>
>> # modprobe acpi-cpufreq
>> FATAL: Error inserting acpi_cpufreq
>> (/lib/modules/2.6.23.12-pata-1/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko):
>> No such device
>
> Have you checked whether that the CPU is cpufreq capable at all?
According to Documentation/cpu-freq/user-guide.txt, Intel Xeon is
supported by cpufreq. Are there exceptions to that (i.e., some Xeons are
not supported)?
Anyway, "cat /dev/zero >/dev/null" scales the frequency up; reading from
a dm-crypt device doesn't.
> If yes, you might want to upgrade the BIOS.
>
> Still, it looks strange that frequency (in this case throttling) is not
> set to the highest state as measuring the idle time should be the same
> mechanism and low-level driver independent. So this may be a valid bug,
> but using p4-clockmode is not a good idea to work on it (p4-clockmode is
> not a good idea to work on in general, IMO it should vanish totally...).
In that case, it's not documented very clearly (in "make menuconfig").
Basically, a P4 user can pick either:
CONFIG_X86_ACPI_CPUFREQ:
This driver adds a CPUFreq driver which utilizes the ACPI
Processor Performance States.
This driver also supports Intel Enhanced Speedstep.
or:
CONFIG_X86_P4_CLOCKMOD:
This adds the CPUFreq driver for Intel Pentium 4 / XEON
processors.
CONFIG_X86_P4_CLOCKMOD is more explicit and implies that is the
preferred module for a P4 CPU.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2008-01-14 10:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 22:15 Overall picture of cpufreq Saru Addep
2008-01-11 22:50 ` Leisner, Martin
2008-01-13 22:54 ` Thomas Renninger
2008-01-14 2:12 ` Saru Addep
2008-01-14 7:08 ` Tomasz Chmielewski
2008-01-14 7:51 ` Saru Addep
2008-01-14 9:51 ` Thomas Renninger
2008-01-14 10:16 ` Tomasz Chmielewski
2008-01-14 10:32 ` Thomas Renninger
2008-01-14 10:59 ` Tomasz Chmielewski [this message]
2008-01-14 19:13 ` Saru Addep
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=478B4097.8010401@wpkg.org \
--to=mangoo@wpkg.org \
--cc=Martin.Leisner@xerox.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=trenn@suse.de \
/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