From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Dirk Brandewie <dirk.j.brandewie@intel.com>,
Shreyas Prabhu <shreyas@linux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Patrick Marlier <patrick.marlier@gmail.com>,
Dirk Brandewie <dirk.brandewie@gmail.com>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] powernv/cpufreq: Set the pstate of the last hotplugged out cpu in policy->cpus to minimum
Date: Fri, 05 Sep 2014 12:48:30 +0530 [thread overview]
Message-ID: <540963C6.8010702@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAKohpokThCn3ze7KZ0zZNN8zyVCxjdL=pGBhWcAvVr9T23RxSg@mail.gmail.com>
On 09/05/2014 12:37 PM, Viresh Kumar wrote:
> On 5 September 2014 12:31, Preeti U Murthy <preeti@linux.vnet.ibm.com> wrote:
>
>> + smp_call_function_any(policy->cpus, set_pstate, &freq_data, 1);
>
> We will surely have a single CPU alive at this point, so should we call
> this function on policy->cpu directly ?
>
Yes that is better. Let me send out an updated version of this patch.
Regards
Preeti U Murthy
prev parent reply other threads:[~2014-09-05 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 7:00 [PATCH 0/2] cpufreq/powernv: Set core pstate to a minimum just before hotplugging it out Preeti U Murthy
2014-09-05 7:01 ` [PATCH 1/2] cpufreq: Allow stop CPU callback to be used by all cpufreq drivers Preeti U Murthy
2014-09-05 7:01 ` [PATCH 2/2] powernv/cpufreq: Set the pstate of the last hotplugged out cpu in policy->cpus to minimum Preeti U Murthy
2014-09-05 7:07 ` Viresh Kumar
2014-09-05 7:18 ` Preeti U Murthy [this message]
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=540963C6.8010702@linux.vnet.ibm.com \
--to=preeti@linux.vnet.ibm.com \
--cc=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patrick.marlier@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=shreyas@linux.vnet.ibm.com \
--cc=svaidy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.