From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH v2] cpufreq: stats: Walk online CPUs with CPU offline/online locked
Date: Fri, 20 May 2016 07:52:47 +0530 [thread overview]
Message-ID: <20160520022247.GS32001@vireshk-i7> (raw)
In-Reply-To: <2278154.xyiFOocWfq@vostro.rjw.lan>
On 20-05-16, 03:41, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Loops over online CPUs in cpufreq_stats_init() and cpufreq_stats_exit()
> should be carried out with CPU offline/online locked or races are
> possible otherwise, so make that happen.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
>
> v1 -> v2: On a second thought, add the policy notifier in cpufreq_stats_init()
> with CPU offline/online locked too.
>
> ---
> drivers/cpufreq/cpufreq_stats.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> Index: linux-pm/drivers/cpufreq/cpufreq_stats.c
> ===================================================================
> --- linux-pm.orig/drivers/cpufreq/cpufreq_stats.c
> +++ linux-pm/drivers/cpufreq/cpufreq_stats.c
> @@ -317,10 +317,13 @@ static int __init cpufreq_stats_init(voi
> unsigned int cpu;
>
> spin_lock_init(&cpufreq_stats_lock);
> +
> + get_online_cpus();
> +
> ret = cpufreq_register_notifier(¬ifier_policy_block,
> CPUFREQ_POLICY_NOTIFIER);
Why is this required to be protected ?
> if (ret)
> - return ret;
> + goto out;
>
> for_each_online_cpu(cpu)
> cpufreq_stats_create_table(cpu);
> @@ -332,21 +335,28 @@ static int __init cpufreq_stats_init(voi
> CPUFREQ_POLICY_NOTIFIER);
> for_each_online_cpu(cpu)
> cpufreq_stats_free_table(cpu);
Maybe we can make this for_each_possible_cpu() then, and so getting a
policy will fail for CPUs which aren't online.
And we wouldn't need to use get_online_cpus() then ?
--
viresh
next prev parent reply other threads:[~2016-05-20 2:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 1:34 [PATCH] cpufreq: stats: Walk online CPUs with CPU offline/online locked Rafael J. Wysocki
2016-05-20 1:41 ` [PATCH v2] " Rafael J. Wysocki
2016-05-20 2:22 ` Viresh Kumar [this message]
2016-05-20 12:13 ` Rafael J. Wysocki
2016-05-20 21:33 ` Rafael J. Wysocki
2016-05-23 3:57 ` Viresh Kumar
2016-05-23 13:40 ` Rafael J. Wysocki
2016-05-23 15:19 ` Viresh Kumar
2016-05-23 20:47 ` Rafael J. Wysocki
2016-05-24 4:56 ` Viresh Kumar
2016-05-24 12:13 ` Rafael J. Wysocki
2016-05-24 12:17 ` Viresh Kumar
2016-05-25 0:00 ` Rafael J. Wysocki
2016-05-25 0:48 ` Rafael J. Wysocki
2016-05-25 2:07 ` 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=20160520022247.GS32001@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.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