public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Yu <yu.c.chen@intel.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Len Brown <lenb@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Zhang Rui <rui.zhang@intel.com>,
	Wendy Wang <wendy.wang@intel.com>
Subject: Re: [PATCH 2/2][v2] cpufreq: intel_pstate: Get percpu max freq via HWP MSR register if available
Date: Tue, 12 Jan 2021 11:28:22 +0800	[thread overview]
Message-ID: <20210112032822.GA28619@chenyu-office.sh.intel.com> (raw)
In-Reply-To: <7a7de1fedb49489fddf7eac791149f546adccad1.camel@linux.intel.com>

On Mon, Jan 11, 2021 at 03:11:02AM -0800, Srinivas Pandruvada wrote:
> On Mon, 2021-01-11 at 15:43 +0800, Chen Yu wrote:
> > Currently when turbo is disabled(either by BIOS or by the user), the
> > intel_pstate
> > driver reads the max frequency from the package-wide
> > MSR_PLATFORM_INFO(0xce) register.
> > However on asymmetric platforms it is possible in theory that small
> > and big core with
> > HWP enabled might have different max cpu frequency
> max non-turbo frequency (although code call max_freq).
>
Okay, will change.

Thanks,
Chenyu
> Thanks,
> Srinivas
> 

      reply	other threads:[~2021-01-12  3:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11  7:43 [PATCH 0/2][v2] Get percpu max freq via HWP MSR register Chen Yu
2021-01-11  7:43 ` [PATCH 1/2][v2] cpufreq: intel_pstate: Add parameter to get guarantee frequency Chen Yu
2021-01-11 12:44   ` Rafael J. Wysocki
2021-01-12  3:29     ` Chen Yu
2021-01-11  7:43 ` [PATCH 2/2][v2] cpufreq: intel_pstate: Get percpu max freq via HWP MSR register if available Chen Yu
2021-01-11 11:11   ` Srinivas Pandruvada
2021-01-12  3:28     ` Chen Yu [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=20210112032822.GA28619@chenyu-office.sh.intel.com \
    --to=yu.c.chen@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=viresh.kumar@linaro.org \
    --cc=wendy.wang@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