linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: len.brown@intel.com, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: intel_pstate: Enable HWP by default
Date: Thu, 25 Feb 2016 15:33:51 -0800	[thread overview]
Message-ID: <1456443231.17628.24.camel@linux.intel.com> (raw)
In-Reply-To: <7409824.yRBnCff0bU@vostro.rjw.lan>

On Fri, 2016-02-26 at 00:19 +0100, Rafael J. Wysocki wrote:
> On Thursday, February 25, 2016 03:09:19 PM Srinivas Pandruvada wrote:
> > If the processor supports HWP, enable it by default without
> > checking
> > for the cpu model. This will allow to enable HWP in all supported
> > processors without driver change.
> > 
> > Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel
> > .com>
> 
> Isn't that a bit risky in the face of recent experience?
Good question. The current systems which are commercial, already have
cpuid added in our list, so HWP will be enabled anyway.
The one system we know there is an issue, hope we can debug before
merge window start.
If I don't do, I have to add few more ids to the list.

Let's wait for few more weeks to review and merge this. I will let
anybody from the community comment, who are using Skylake.

Thanks,
Srinivas

> 
> Rafael
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-02-25 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 23:09 [PATCH] cpufreq: intel_pstate: Enable HWP by default Srinivas Pandruvada
2016-02-25 23:19 ` Rafael J. Wysocki
2016-02-25 23:33   ` Srinivas Pandruvada [this message]
2016-02-27  0:02     ` Rafael J. Wysocki

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=1456443231.17628.24.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).