From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Patch Tracking <patches@linaro.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] cpufreq: serialize calls to __cpufreq_governor()
Date: Mon, 02 Sep 2013 14:44:47 +0200 [thread overview]
Message-ID: <59922407.8jDJDIWysm@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpon1VsoUnw=t0c9wQ2Zfva5nnXoKjNNNxLXV7Frto1BFug@mail.gmail.com>
On Sunday, September 01, 2013 09:30:49 PM Viresh Kumar wrote:
> On 1 September 2013 18:58, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Sunday, September 01, 2013 10:56:02 AM Viresh Kumar wrote:
> >> We can't take a big lock around __cpufreq_governor() as this causes recursive
> >> locking for some cases. But calls to this routine must be serialized for every
> >> policy.
> >
> > Care to explain here why it must be serialized?
>
> Yes, added that to the attached patches (Added reported-by too):
OK, the attached patches queued up for 3.12.
Thanks,
Rafael
next prev parent reply other threads:[~2013-09-02 12:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 5:26 [PATCH 1/2] cpufreq: don't allow governor limits to be changed when it is disabled Viresh Kumar
2013-09-01 5:26 ` [PATCH 2/2] cpufreq: serialize calls to __cpufreq_governor() Viresh Kumar
2013-09-01 13:28 ` Rafael J. Wysocki
2013-09-01 16:00 ` Viresh Kumar
2013-09-01 20:27 ` Rafael J. Wysocki
2013-09-02 1:00 ` Viresh Kumar
2013-09-02 12:44 ` Rafael J. Wysocki [this message]
2013-09-03 13:20 ` Srivatsa S. Bhat
2013-09-03 19:40 ` Rafael J. Wysocki
2013-09-13 11:44 ` Viresh Kumar
2013-09-13 23:48 ` Rafael J. Wysocki
2013-09-14 4:29 ` Viresh Kumar
2013-09-17 11:49 ` Srivatsa S. Bhat
2013-09-04 23:55 ` Rafael J. Wysocki
2013-09-04 23:50 ` Stephen Boyd
2013-09-05 0:26 ` Rafael J. Wysocki
2013-09-05 0:54 ` Stephen Boyd
2013-09-06 6:03 ` Srivatsa S. Bhat
2013-09-06 12:31 ` Rafael J. Wysocki
2013-09-10 6:52 ` Viresh Kumar
2013-09-10 8:47 ` Srivatsa S. Bhat
2013-09-01 6:26 ` [PATCH 1/2] cpufreq: don't allow governor limits to be changed when it is disabled Viresh Kumar
2013-09-01 13:29 ` Rafael J. Wysocki
2013-09-01 13:26 ` 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=59922407.8jDJDIWysm@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=sboyd@codeaurora.org \
--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
all inboxes | Powered by JetHome®