From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Greg KH <greg@kroah.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
SH-Linux <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: "cpufreq: fix serialization issues with freq change notifiers" breaks cpufreq too
Date: Tue, 10 Sep 2013 19:07:39 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1309101853170.16010@axis700.grange> (raw)
In-Reply-To: <CAKohpomK7Y_6aLMA3B+hZrtgYq9U89ihgkbvYWA3BsKN3gJD3g@mail.gmail.com>
On Tue, 10 Sep 2013, Viresh Kumar wrote:
> On 10 September 2013 21:52, Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
> > Of course, isn't that what I've written above? reverted a commit and added
> > debug - in that order.
>
> Ok, I misread it then :(
>
> > Sure, I can... So, with the performance governor I get
> >
> > [ 1.290000] cpufreq-cpu0 cpufreq-cpu0: Looking up cpu0-supply from device tree
> > [ 1.290000] cpufreq: trying to register driver generic_cpu0
> > [ 1.290000] cpufreq: adding CPU 0
> > [ 1.290000] cpufreq: Adding link for CPU: 1
> > [ 1.290000] cpufreq: setting new policy for CPU 0: 398667 - 1196000 kHz
> > [ 1.290000] cpufreq: new min and max freqs are 398667 - 1196000 kHz
> > [ 1.290000] cpufreq: governor switch
> > [ 1.290000] cpufreq: __cpufreq_governor for CPU 0, event 4
> > [ 1.290000] cpufreq: __cpufreq_governor for CPU 0, event 1
> > [ 1.290000] cpufreq_performance: setting to 1196000 kHz because of event 1
> > [ 1.290000] cpufreq: __cpufreq_driver_target().1665 1
> >
> > This is my debug - .transition_ongoing is incremented ^^^^^^^^
> >
> > [ 1.300000] cpufreq: target for CPU 0: 1196000 kHz, relation 1, requested 1196000 kHz
>
> Quite straight forward actually..
Apparently, not quite.
> Please try attached patch and see if it fixes
> your problem.. Which it should if I am not wrong.. I will send it
> separately then..
It helps only once. The first switching works, the second one doesn't.
Below debug
[ 12.010000] cpufreq: setting new policy for CPU 0: 398667 - 1196000 kHz
[ 12.010000] cpufreq: new min and max freqs are 398667 - 1196000 kHz
[ 12.010000] cpufreq: governor switch
[ 12.010000] cpufreq: __cpufreq_governor for CPU 0, event 2
[ 12.010000] cpufreq: __cpufreq_governor for CPU 0, event 5
[ 12.010000] ondemand governor failed, too long transition latency of HW, fallback to performance governor
[ 12.020000] cpufreq: __cpufreq_governor for CPU 0, event 4
[ 12.020000] cpufreq: __cpufreq_governor for CPU 0, event 1
[ 12.020000] cpufreq_performance: setting to 1196000 kHz because of event 1
[ 12.020000] cpufreq: target for CPU 0: 1196000 kHz, relation 1, requested 1196000 kHz
[ 12.020000] cpufreq: governor: change or update limits
[ 12.020000] cpufreq: __cpufreq_governor for CPU 0, event 3
[ 12.020000] cpufreq_performance: setting to 1196000 kHz because of event 3
[ 12.020000] cpufreq: target for CPU 0: 1196000 kHz, relation 1, requested 1196000 kHz
[ 12.030000] cpufreq: setting new policy for CPU 0: 398667 - 1196000 kHz
[ 12.030000] cpufreq: new min and max freqs are 398667 - 1196000 kHz
[ 12.030000] cpufreq: governor switch
[ 12.030000] cpufreq: __cpufreq_governor for CPU 0, event 2
[ 12.030000] cpufreq: __cpufreq_governor for CPU 0, event 5
[ 12.030000] ondemand governor failed, too long transition latency of HW, fallback to performance governor
[ 12.040000] cpufreq: __cpufreq_governor for CPU 0, event 4
[ 12.040000] cpufreq: __cpufreq_governor for CPU 0, event 1
[ 12.040000] cpufreq_performance: setting to 1196000 kHz because of event 1
[ 12.040000] cpufreq: target for CPU 0: 1196000 kHz, relation 1, requested 1196000 kHz
[ 12.040000] cpufreq: governor: change or update limits
[ 12.040000] cpufreq: __cpufreq_governor for CPU 0, event 3
[ 12.040000] cpufreq_performance: setting to 1196000 kHz because of event 3
[ 12.040000] cpufreq: target for CPU 0: 1196000 kHz, relation 1, requested 1196000 kHz
echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
[ 66.490000] cpufreq: setting new policy for CPU 0: 398667 - 1196000 kHz
[ 66.490000] cpufreq: new min and max freqs are 398667 - 1196000 kHz
[ 66.490000] cpufreq: governor switch
[ 66.490000] cpufreq: __cpufreq_governor for CPU 0, event 2
[ 66.490000] cpufreq: __cpufreq_governor for CPU 0, event 5
[ 66.490000] cpufreq: __cpufreq_governor for CPU 0, event 4
[ 66.490000] cpufreq: __cpufreq_governor for CPU 0, event 1
[ 66.490000] cpufreq: target for CPU 0: 398667 kHz, relation 0, requested 398667 kHz
[ 66.490000] cpufreq: __cpufreq_driver_target().1677 1
[ 66.500000] cpufreq: notification 0 of frequency transition to 398666 kHz
[ 66.500000] cpufreq: __cpufreq_notify_transition().297 2
[ 66.500000] cpufreq: notification 0 of frequency transition to 398666 kHz
[ 66.500000] cpufreq: __cpufreq_notify_transition().297 3
[ 66.510000] cpufreq: notification 1 of frequency transition to 398666 kHz
[ 66.510000] cpufreq: __cpufreq_notify_transition().327 2
[ 66.520000] cpufreq: FREQ: 398666 - CPU: 0
[ 66.520000] cpufreq: notification 1 of frequency transition to 398666 kHz
[ 66.520000] cpufreq: __cpufreq_notify_transition().327 1
[ 66.520000] cpufreq: FREQ: 398666 - CPU: 1
[ 66.520000] cpufreq: cpufreq_notify_transition().366 0
[ 66.530000] cpufreq: governor: change or update limits
[ 66.530000] cpufreq: __cpufreq_governor for CPU 0, event 3
[ 66.530000] cpufreq: target for CPU 0: 398667 kHz, relation 0, requested 398667 kHz
[ 66.530000] cpufreq: __cpufreq_driver_target().1677 1
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
[ 72.470000] cpufreq: setting new policy for CPU 0: 398667 - 1196000 kHz
[ 72.470000] cpufreq: new min and max freqs are 398667 - 1196000 kHz
[ 72.470000] cpufreq: governor switch
[ 72.470000] cpufreq: __cpufreq_governor for CPU 0, event 2
[ 72.470000] cpufreq: __cpufreq_governor for CPU 0, event 5
[ 72.470000] cpufreq: __cpufreq_governor for CPU 0, event 4
[ 72.470000] cpufreq: __cpufreq_governor for CPU 0, event 1
[ 72.470000] cpufreq_performance: setting to 1196000 kHz because of event 1
[ 72.470000] cpufreq: target for CPU 0: 1196000 kHz, relation 1, requested 1196000 kHz
[ 72.470000] cpufreq: governor: change or update limits
[ 72.470000] cpufreq: __cpufreq_governor for CPU 0, event 3
[ 72.470000] cpufreq_performance: setting to 1196000 kHz because of event 3
[ 72.470000] cpufreq: target for CPU 0: 1196000 kHz, relation 1, requested 1196000 kHz
> Thanks for your time..
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2013-09-10 17:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 15:11 "cpufreq: fix serialization issues with freq change notifiers" breaks cpufreq too Guennadi Liakhovetski
2013-09-09 21:08 ` Rafael J. Wysocki
2013-09-09 21:42 ` Guennadi Liakhovetski
2013-09-09 23:12 ` Rafael J. Wysocki
2013-09-10 1:46 ` Rafael J. Wysocki
2013-09-10 11:29 ` Viresh Kumar
2013-09-10 11:49 ` Rafael J. Wysocki
2013-09-10 15:14 ` Viresh Kumar
2013-09-10 19:46 ` Rafael J. Wysocki
2013-09-11 8:38 ` Viresh Kumar
2013-09-11 13:18 ` Rafael J. Wysocki
2013-09-12 0:39 ` Viresh Kumar
2013-09-12 0:43 ` Rafael J. Wysocki
2013-09-12 5:36 ` Viresh Kumar
2013-09-12 11:01 ` Rafael J. Wysocki
2013-09-12 10:52 ` Viresh Kumar
2013-09-10 15:12 ` Guennadi Liakhovetski
2013-09-10 15:26 ` Viresh Kumar
2013-09-10 16:22 ` Guennadi Liakhovetski
2013-09-10 16:34 ` Viresh Kumar
2013-09-10 17:07 ` Guennadi Liakhovetski [this message]
2013-09-11 8:06 ` Viresh Kumar
2013-09-11 8:15 ` Guennadi Liakhovetski
2013-09-11 8:39 ` Viresh Kumar
2013-09-11 13:28 ` Rafael J. Wysocki
2013-09-12 7:47 ` Guennadi Liakhovetski
2013-09-12 7:51 ` 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=Pine.LNX.4.64.1309101853170.16010@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=cpufreq@vger.kernel.org \
--cc=greg@kroah.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rafael.j.wysocki@intel.com \
--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