From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: ego@linux.vnet.ibm.com
Cc: Linux PM list <linux-pm@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Anton Blanchard <anton@samba.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Subject: Re: [PATCH v4] powernv, cpufreq: cpufreq driver for powernv platform
Date: Thu, 27 Mar 2014 23:56:17 +1100 [thread overview]
Message-ID: <1395924977.5569.109.camel@pasglop> (raw)
In-Reply-To: <20140327112031.GC27777@in.ibm.com>
On Thu, 2014-03-27 at 16:50 +0530, Gautham R Shenoy wrote:
>
> Well, in the scenarios that we're interested in, it is highly unlikely
> that CONFIG_PREMPT is set. Hence we'll default to
> raw_smp_processor_id() anyway. So, I think we can retain
> smp_processor_id().
We don't know that. Some people are interested in running preempt
on these things. If raw is ok to call here, please use it.
Cheers,
Ben.
next prev parent reply other threads:[~2014-03-27 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 16:55 [PATCH v4] powernv: Dynamic Frequency Scaling Enablement Gautham R. Shenoy
2014-03-26 16:55 ` [PATCH v4] powernv, cpufreq: cpufreq driver for powernv platform Gautham R. Shenoy
2014-03-27 3:56 ` Anton Blanchard
2014-03-27 6:39 ` Viresh Kumar
2014-03-27 9:30 ` Gautham R Shenoy
2014-03-27 9:59 ` Viresh Kumar
2014-03-27 10:21 ` Srivatsa S. Bhat
2014-03-27 10:23 ` Viresh Kumar
2014-03-27 11:20 ` Gautham R Shenoy
2014-03-27 11:29 ` Viresh Kumar
2014-03-27 12:56 ` Benjamin Herrenschmidt [this message]
2014-03-27 10:11 ` Vaidyanathan Srinivasan
2014-03-27 10:22 ` Viresh Kumar
2014-03-27 11:12 ` Benjamin Herrenschmidt
2014-03-28 5:25 ` Viresh Kumar
2014-03-27 5:38 ` [PATCH v4] powernv: Dynamic Frequency Scaling Enablement Viresh Kumar
2014-03-27 6:28 ` Benjamin Herrenschmidt
2014-03-27 6:42 ` 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=1395924977.5569.109.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=anton@samba.org \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rjw@rjwysocki.net \
--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).