From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Dave Jones" <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Ondemand/Conservative not working with 2.6.18
Date: Wed, 11 Oct 2006 22:39:44 +0300 [thread overview]
Message-ID: <200610112239.44100.caglar@pardus.org.tr> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A8454B6C08C@scsmsx413.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]
11 Eki 2006 Çar 22:00 tarihinde, Pallipadi, Venkatesh şunları yazmıştı:
> Can you configure with CPU_FREQ_DEBUG and do "echo 5 >
> /sys/module/cpufreq/parameter/debug" before switching the governor to
> ondemand and see whether you see any messages in dmesg?
Here it is (sorry for prev. uncomplete mail);
zangetsu cpufreq # echo 5 > /sys/module/cpufreq/parameters/debug
zangetsu cpufreq # echo "ondemand" > scaling_governor
zangetsu cpufreq # dmesg
...
cpufreq-core: setting new policy for CPU 0: 800000 - 1733000 kHz
freq-table: request for verification of policy (800000 - 1733000 kHz) for cpu
0
freq-table: verification lead to (800000 - 1733000 kHz) for cpu 0
freq-table: request for verification of policy (800000 - 1733000 kHz) for cpu
0
freq-table: verification lead to (800000 - 1733000 kHz) for cpu 0
cpufreq-core: new min and max freqs are 800000 - 1733000 kHz
cpufreq-core: governor switch
cpufreq-core: __cpufreq_governor for CPU 0, event 2
cpufreq-core: __cpufreq_governor for CPU 0, event 1
cpufreq-core: governor: change or update limits
cpufreq-core: __cpufreq_governor for CPU 0, event 3
cpufreq-core: target for CPU 0: 1510185 kHz, relation 0
freq-table: request for target 1510185 kHz (relation: 0) for cpu 0
freq-table: target is 0 (1733000 kHz, 3369)
cpufreq-core: target for CPU 0: 1609214 kHz, relation 0
freq-table: request for target 1609214 kHz (relation: 0) for cpu 0
freq-table: target is 0 (1733000 kHz, 3369)
cpufreq-core: target for CPU 0: 1633971 kHz, relation 0
freq-table: request for target 1633971 kHz (relation: 0) for cpu 0
freq-table: target is 0 (1733000 kHz, 3369)
cpufreq-core: target for CPU 0: 1559700 kHz, relation 0
freq-table: request for target 1559700 kHz (relation: 0) for cpu 0
freq-table: target is 0 (1733000 kHz, 3369)
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-11 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 19:00 Ondemand/Conservative not working with 2.6.18 Pallipadi, Venkatesh
2006-10-11 19:08 ` S.Çağlar Onur
2006-10-11 19:38 ` S.Çağlar Onur
2006-10-11 19:39 ` S.Çağlar Onur [this message]
2006-10-13 18:33 ` S.Çağlar Onur
-- strict thread matches above, loose matches on Subject: below --
2006-10-16 13:08 Pallipadi, Venkatesh
2006-10-16 20:29 ` S.Çağlar Onur
2006-10-09 23:35 Pallipadi, Venkatesh
2006-10-10 20:54 ` S.Çağlar Onur
2006-10-04 13:33 S.Çağlar Onur
2006-10-09 21:52 ` S.Çağlar Onur
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=200610112239.44100.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.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.