From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
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: Tue, 24 May 2016 17:47:17 +0530 [thread overview]
Message-ID: <20160524121717.GY17585@vireshk-i7> (raw)
In-Reply-To: <2500818.MtOb9b1ZsB@vostro.rjw.lan>
On 24-05-16, 14:13, Rafael J. Wysocki wrote:
> I don't really get it why you don't like get/put_online_cpus() so much.
Not that I don't like them, I just wanted to see if its possible to
work without any additional locking.
Anyway, so the first version of your patch did the get_online_cpus()
around a bigger section of the code instead of just the
for_each_online_cpu() loop. Should we change that?
--
viresh
next prev parent reply other threads:[~2016-05-24 12:17 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
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 [this message]
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=20160524121717.GY17585@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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