From: Stephen Boyd <sboyd@codeaurora.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] cpufreq: serialize calls to __cpufreq_governor()
Date: Wed, 04 Sep 2013 16:50:01 -0700 [thread overview]
Message-ID: <5227C729.5040803@codeaurora.org> (raw)
In-Reply-To: <1706734.hVYFTCa5rJ@vostro.rjw.lan>
On 09/04/13 16:55, Rafael J. Wysocki wrote:
>
> Well, I'm not sure when Viresh is going to be back.
>
> Srivatsa, can you please resend this patch with a proper changelog?
>
I haven't had a chance to try this out yet, but I was just thinking
about this patch. How is it going to work? If one task opens the file
and another task is taking down the CPU wouldn't we deadlock in the
CPU_DOWN notifier waiting for the kobject to be released? Task 1 will
grab the kobject reference and sleep on the hotplug mutex and task 2
will put the kobject and wait for the completion, but it won't happen.
At least I think that's what would happen.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-09-04 23:50 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
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 [this message]
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=5227C729.5040803@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).