All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	dirk.j.brandewie@intel.com
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-pm@vger.kernel.org, Daniel Vetter <daniel.vetter@intel.com>,
	lenb@kernel.org
Subject: Re: CPUfreq lockdep issue
Date: Fri, 19 Feb 2016 14:35:44 -0800	[thread overview]
Message-ID: <1455921344.8680.36.camel@linux.intel.com> (raw)
In-Reply-To: <20160219091723.GB22812@vireshk-i7>

On Fri, 2016-02-19 at 14:47 +0530, Viresh Kumar wrote:
> Adding the maintainers of the driver in cc now.
[...]
Hi Viresh,
> Hi Guys,
> 
> Joonas reported a lockdep between cpufreq and intel-pstate driver and
> we are looking for probable solutions.
> 
> I failed to understand why should we run intel_pstate_hwp_set() for
> each online CPU, while the frequency is changed only for a group of
> CPUs that belong to a policy. 
Don't need from set_policy interface. 
> Ofcourse intel_pstate_hwp_set() is
> required to be run for all CPUs, while the sysfs files are touched.
> And so, do we have a problem with below diff?
I gave a quick test, the change works fine.

Thanks,
Srinivas


  reply	other threads:[~2016-02-19 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 11:06 CPUfreq lockdep issue Joonas Lahtinen
2016-02-18 11:34 ` Viresh Kumar
2016-02-19  8:50   ` Joonas Lahtinen
2016-02-19  9:17     ` Viresh Kumar
2016-02-19 22:35       ` Srinivas Pandruvada [this message]
2016-02-19 23:14         ` Rafael J. Wysocki
2016-02-22  9:10 ` 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=1455921344.8680.36.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dirk.j.brandewie@intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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.