From: Xiaoguang Chen <chenxg.marvell@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Xiaoguang Chen <chenxg@marvell.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
njiang1@marvell.com, zjwu@marvell.com, ylmao@marvell.com
Subject: Re: [PATCH v5] cpufreq: fix governor start/stop race condition
Date: Thu, 13 Jun 2013 18:03:12 +0800 [thread overview]
Message-ID: <CAFgnuDe-Noa7sn2fjMEqY-tVV2FMXeZBm07m8e-0LRQvqAWbeA@mail.gmail.com> (raw)
In-Reply-To: <CAKohpomDXmQ_DWpHgm1mD5WWUvBTjWXBPDp1KOWb1mff4UdX=g@mail.gmail.com>
2013/6/13 Viresh Kumar <viresh.kumar@linaro.org>:
> On 13 June 2013 14:31, Xiaoguang Chen <chenxg@marvell.com> wrote:
>> cpufreq governor stop and start should be kept in sequence.
>> If not, there will be unexpected behavior, for example:
>>
>> we have 4 cpus and policy->cpu=cpu0, cpu1/2/3 are linked to cpu0.
>> the normal sequence is as below:
>>
>> 1) Current governor is userspace, one application tries to set
>> governor to ondemand. it will call __cpufreq_set_policy in which it
>> will stop userspace governor and then start ondemand governor.
>>
>> 2) Current governor is userspace, now cpu0 hotplugs in cpu3, it will
>> call cpufreq_add_policy_cpu. on which it first stops userspace
>> governor, and then starts userspace governor.
>>
>> Now if the sequence of above two cases interleaves, it becames
>> below sequence:
>>
>> 1) application stops userspace governor
>> 2) hotplug stops userspace governor
>> 3) application starts ondemand governor
>> 4) hotplug starts a governor
>>
>> in step 4, hotplug is supposed to start userspace governor, but now
>> the governor has been changed by application to ondemand, so hotplug
>> starts ondemand governor again !!!!
>>
>> The solution is: do not allow stop one policy's governor multi-times
>> Governor stop should only do once for one policy, after it is stopped,
>> no other governor stop should be executed. also add one mutext to
>> protect __cpufreq_governor so governor operation can be kept in sequence.
>>
>> Signed-off-by: Xiaoguang Chen <chenxg@marvell.com>
>> ---
>> drivers/cpufreq/cpufreq.c | 24 ++++++++++++++++++++++++
>> include/linux/cpufreq.h | 1 +
>> 2 files changed, 25 insertions(+)
>
> I forgot to tell you earlier but please update changelog everytime you
> send a new version.
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Thanks
I'll pay attention next time :)
Xiaoguang
next prev parent reply other threads:[~2013-06-13 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 9:01 [PATCH v5] cpufreq: fix governor start/stop race condition Xiaoguang Chen
2013-06-13 9:16 ` Viresh Kumar
2013-06-13 10:03 ` Xiaoguang Chen [this message]
2013-06-19 0:25 ` Rafael J. Wysocki
2013-06-19 1:20 ` Xiaoguang Chen
2013-06-19 3:00 ` Viresh Kumar
2013-06-19 22:49 ` Rafael J. Wysocki
2013-06-20 3:46 ` Viresh Kumar
2013-06-19 3:13 ` Viresh Kumar
2013-06-19 3:15 ` Viresh Kumar
2013-06-19 3:26 ` Xiaoguang Chen
2013-06-19 22:50 ` Rafael J. Wysocki
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=CAFgnuDe-Noa7sn2fjMEqY-tVV2FMXeZBm07m8e-0LRQvqAWbeA@mail.gmail.com \
--to=chenxg.marvell@gmail.com \
--cc=chenxg@marvell.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=njiang1@marvell.com \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.org \
--cc=ylmao@marvell.com \
--cc=zjwu@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).