From: "Kasagar, Srinidhi" <srinidhi.kasagar@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Dirk Brandewie <dirk.j.brandewie@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
vishwesh.m.rudramuni@intel.com
Subject: Re: [PATCH] cpufreq: Add sfi based cpufreq driver support
Date: Fri, 10 Oct 2014 00:37:48 +0530 [thread overview]
Message-ID: <20141009190747.GA31674@intel-desktop> (raw)
In-Reply-To: <CAKohpok9d4AK4qmERqtnGYBtZx=wnP5fdECOT6t1NFEGfAQ_2g@mail.gmail.com>
On Thu, Oct 09, 2014 at 03:48:08PM +0530, Viresh Kumar wrote:
> On 9 October 2014 23:38, Kasagar, Srinidhi <srinidhi.kasagar@intel.com> wrote:
> > I guess if you offline a cpu and then bring it online, then even though
> > there is no change in frequency, the core calls ->target_index().
>
> No.
Hmm..I noticed later that I was doing cpumask_copy for my internal experiments.
Even in that case, as you pointed, the ->target_index() was not called
for the onlined CPU, but for the other related CPU. I should have
debug printed policy->cpu in my ->target() implementation..:(
Anyway, thanks much for it. Will fix that useless check in the next version
of my patch.
Srinidhi
next prev parent reply other threads:[~2014-10-09 11:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 14:07 [PATCH] cpufreq: Add sfi based cpufreq driver support Kasagar, Srinidhi
2014-10-07 10:22 ` Viresh Kumar
2014-10-08 19:14 ` Kasagar, Srinidhi
2014-10-09 4:03 ` Viresh Kumar
2014-10-09 18:08 ` Kasagar, Srinidhi
2014-10-09 10:18 ` Viresh Kumar
2014-10-09 19:07 ` Kasagar, Srinidhi [this message]
2014-10-09 11:15 ` Viresh Kumar
2014-10-10 16:51 ` Kasagar, Srinidhi
2014-10-10 8:57 ` Viresh Kumar
2014-10-10 17:14 ` Kasagar, Srinidhi
2014-10-10 9:27 ` Viresh Kumar
2014-10-10 10:47 ` Kasagar, Srinidhi
2014-10-10 11:11 ` 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=20141009190747.GA31674@intel-desktop \
--to=srinidhi.kasagar@intel.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=vishwesh.m.rudramuni@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;
as well as URLs for NNTP newsgroup(s).