From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Borislav Petkov <bp@alien8.de>, Jiri Kosina <jkosina@suse.cz>,
Tomasz Figa <t.figa@samsung.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [v3.10 regression] deadlock on cpu hotplug
Date: Wed, 10 Jul 2013 10:40:48 +0800 [thread overview]
Message-ID: <51DCC9B0.9090507@linux.vnet.ibm.com> (raw)
In-Reply-To: <1754044.EVIH1UZj6p@amdc1032>
On 07/09/2013 07:51 PM, Bartlomiej Zolnierkiewicz wrote:
[snip]
>
> It doesn't help and unfortunately it just can't help as it only
> addresses lockdep functionality while the issue is not a lockdep
> problem but a genuine locking problem. CPU hot-unplug invokes
> _cpu_down() which calls cpu_hotplug_begin() which in turn takes
> &cpu_hotplug.lock. The lock is then hold during __cpu_notify()
> call. Notifier chain goes up to cpufreq_governor_dbs() which for
> CPUFREQ_GOV_STOP event does gov_cancel_work(). This function
> flushes pending work and waits for it to finish. The all above
> happens in one kernel thread. At the same time the other kernel
> thread is doing the work we are waiting to complete and it also
> happens to do gov_queue_work() which calls get_online_cpus().
> Then the code tries to take &cpu_hotplug.lock which is already
> held by the first thread and deadlocks.
Hmm...I think I get your point, some thread hold the lock and
flush some work which also try to hold the same lock, correct?
Ok, that's a problem, let's figure out a good way to solve it :)
Regards,
Michael Wang
>
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
>
>> diff --git a/drivers/cpufreq/cpufreq_governor.c b/drivers/cpufreq/cpufreq_governor.c
>> index 5af40ad..aa05eaa 100644
>> --- a/drivers/cpufreq/cpufreq_governor.c
>> +++ b/drivers/cpufreq/cpufreq_governor.c
>> @@ -229,6 +229,8 @@ static void set_sampling_rate(struct dbs_data *dbs_data,
>> }
>> }
>>
>> +static struct lock_class_key j_cdbs_key;
>> +
>> int cpufreq_governor_dbs(struct cpufreq_policy *policy,
>> struct common_dbs_data *cdata, unsigned int event)
>> {
>> @@ -366,6 +368,8 @@ int (struct cpufreq_policy *policy,
>> kcpustat_cpu(j).cpustat[CPUTIME_NICE];
>>
>> mutex_init(&j_cdbs->timer_mutex);
>> + lockdep_set_class(&j_cdbs->timer_mutex, &j_cdbs_key);
>> +
>> INIT_DEFERRABLE_WORK(&j_cdbs->work,
>> dbs_data->cdata->gov_dbs_timer);
>> }
>>
>> Regards,
>> Michael Wang
>
next prev parent reply other threads:[~2013-07-10 2:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 15:26 [v3.10 regression] deadlock on cpu hotplug Bartlomiej Zolnierkiewicz
2013-07-09 2:15 ` Michael Wang
2013-07-09 11:51 ` Bartlomiej Zolnierkiewicz
2013-07-09 13:07 ` Srivatsa S. Bhat
2013-07-10 3:29 ` Michael Wang
2013-07-10 4:12 ` Michael Wang
2013-07-10 5:39 ` Viresh Kumar
2013-07-10 6:04 ` Michael Wang
2013-07-10 6:34 ` Viresh Kumar
2013-07-10 2:40 ` Michael Wang [this message]
2013-07-10 8:57 ` Michael Wang
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=51DCC9B0.9090507@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=b.zolnierkie@samsung.com \
--cc=bp@alien8.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=t.figa@samsung.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).