From: Stephen Warren <swarren@wwwdotorg.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J . Wysocki" <rjw@sisk.pl>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: cpufreq regression due to dceff5c "cpufreq: fix serialization issues with freq change notifiers"
Date: Wed, 11 Sep 2013 16:20:36 -0600 [thread overview]
Message-ID: <5230ECB4.2090306@wwwdotorg.org> (raw)
One of the test cases I run (not often enough, hence I just noticed this
late) is the following, to make sure our cpufreq driver is present, and
adjusting the CPU clock as expected:
# echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq ;
sleep 1 ; cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq ;
echo 216000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq ;
sleep 1 ; cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
which prints the following when it works:
1000000
216000
In next-20130909, that doesn't work, but instead prints:
216000
216000
I've also seen the following during git bisect:
608000
608000
... and perhaps other unexpected sets of values.
This is a regression. I found that if I revert dceff5c "cpufreq: fix
serialization issues with freq change notifiers", then the test case
works as expected.
Any idea what's up?
next reply other threads:[~2013-09-11 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 22:20 Stephen Warren [this message]
2013-09-11 22:51 ` cpufreq regression due to dceff5c "cpufreq: fix serialization issues with freq change notifiers" Rafael J. Wysocki
2013-09-11 22:53 ` Stephen Warren
2013-09-12 0:18 ` Rafael J. Wysocki
2013-09-12 0:26 ` Viresh Kumar
2013-09-12 0:31 ` Viresh Kumar
2013-09-12 16:27 ` Stephen Warren
2013-09-13 4:21 ` Viresh Kumar
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=5230ECB4.2090306@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.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