public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org
Cc: daniel.sneddon@linux.intel.com, tony.luck@intel.com,
	 linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	 linux-perf-users@vger.kernel.org,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	 "Rafael J. Wysocki" <rafael@kernel.org>,
	Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
	 "Liang, Kan" <kan.liang@linux.intel.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH PATCH 2/9] cpufreq: intel_pstate: Use topology_cpu_type() to get cpu-type
Date: Mon, 17 Jun 2024 02:27:02 -0700	[thread overview]
Message-ID: <27018603c7ed574451520aeeae405f7b1fcd6c4e.camel@linux.intel.com> (raw)
In-Reply-To: <20240617-add-cpu-type-v1-2-b88998c01e76@linux.intel.com>

On Mon, 2024-06-17 at 02:11 -0700, Pawan Gupta wrote:
> Intel pstate driver uses hybrid_get_type() to get the cpu-type of a
> given
> CPU. It uses smp_call_function_single() which is sub-optimal and can
> be
> avoided as cpu-type is also available in the per-cpu topology
> structure.
> 
> Use topology_cpu_type() to get the cpu-type.
> 
> Signed-off-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>

> ---
>  drivers/cpufreq/intel_pstate.c | 14 +++-----------
>  1 file changed, 3 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/cpufreq/intel_pstate.c
> b/drivers/cpufreq/intel_pstate.c
> index 65d3f79104bd..40f5e5b0b45e 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -1951,24 +1951,16 @@ static int knl_get_turbo_pstate(int cpu)
>  	return ret;
>  }
>  
> -static void hybrid_get_type(void *data)
> -{
> -	u8 *cpu_type = data;
> -
> -	*cpu_type = get_this_hybrid_cpu_type();
> -}
> -
>  static int hwp_get_cpu_scaling(int cpu)
>  {
> -	u8 cpu_type = 0;
> +	u8 cpu_type = topology_cpu_type(cpu);
>  
> -	smp_call_function_single(cpu, hybrid_get_type, &cpu_type,
> 1);
>  	/* P-cores have a smaller perf level-to-freqency scaling
> factor. */
> -	if (cpu_type == 0x40)
> +	if (cpu_type == X86_CPU_TYPE_INTEL_CORE)
>  		return hybrid_scaling_factor;
>  
>  	/* Use default core scaling for E-cores */
> -	if (cpu_type == 0x20)
> +	if (cpu_type == X86_CPU_TYPE_INTEL_ATOM)
>  		return core_get_scaling();
>  
>  	/*
> 


  reply	other threads:[~2024-06-17  9:27 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  9:11 [PATCH 0/9] Add CPU-type to topology Pawan Gupta
2024-06-17  9:11 ` [PATCH PATCH 1/9] x86/cpu/topology: Add x86_cpu_type to struct cpuinfo_topology Pawan Gupta
2024-06-17  9:35   ` Andrew Cooper
2024-06-17 17:51     ` Pawan Gupta
2024-06-17 13:24   ` kernel test robot
2024-06-17 13:45   ` kernel test robot
2024-06-18 21:28   ` Borislav Petkov
2024-06-19  3:31     ` Pawan Gupta
2024-06-20 15:51       ` Borislav Petkov
2024-06-21  6:36         ` Pawan Gupta
2024-06-18 21:33   ` Mario Limonciello
2024-06-18 22:03     ` Dave Hansen
2024-06-17  9:11 ` [PATCH PATCH 2/9] cpufreq: intel_pstate: Use topology_cpu_type() to get cpu-type Pawan Gupta
2024-06-17  9:27   ` srinivas pandruvada [this message]
2024-06-17 18:36     ` Pawan Gupta
2024-06-17 14:01   ` kernel test robot
2024-06-17  9:11 ` [PATCH PATCH 3/9] perf/x86/intel: " Pawan Gupta
2024-06-17 14:50   ` Dave Hansen
2024-06-17 18:09     ` Pawan Gupta
2024-06-17 18:17       ` Dave Hansen
2024-06-17 18:25         ` Pawan Gupta
2024-06-17  9:11 ` [PATCH PATCH 4/9] x86/cpu: Remove get_this_hybrid_cpu_type() Pawan Gupta
2024-06-17  9:11 ` [PATCH PATCH 5/9] x86/cpu: Name CPU matching macro more generically (and shorten) Pawan Gupta
2024-06-17  9:11 ` [PATCH PATCH 6/9] x86/cpu: Add cpu_type to struct x86_cpu_id Pawan Gupta
2024-06-17  9:12 ` [PATCH PATCH 7/9] x86/cpu: Update x86_match_cpu() to also use cpu-type Pawan Gupta
2024-06-17  9:12 ` [PATCH PATCH 8/9] x86/bugs: Declutter vulnerable CPU list Pawan Gupta
2024-06-17  9:38   ` Andrew Cooper
2024-06-17 18:13     ` Pawan Gupta
2024-06-17 14:13   ` Dave Hansen
2024-06-17 18:14     ` Pawan Gupta
2024-06-17 23:52     ` Pawan Gupta
2024-06-18  0:08       ` Luck, Tony
2024-06-18  3:19         ` Pawan Gupta
2024-06-17  9:12 ` [PATCH PATCH 9/9] x86/rfds: Exclude P-only parts from the RFDS affected list Pawan Gupta
2024-06-17  9:43   ` Andrew Cooper
2024-06-17 14:34     ` Dave Hansen
2024-06-17 18:19       ` Pawan Gupta
2024-06-17 14:33   ` Dave Hansen
2024-06-17 18:24     ` Pawan Gupta
2024-06-18 12:49 ` [PATCH 0/9] Add CPU-type to topology Brice Goglin
2024-06-19  1:53   ` Pawan Gupta
2024-06-19 10:34     ` srinivas pandruvada
2024-06-19 21:25       ` Brice Goglin
2024-06-20 15:06         ` Dave Hansen
2024-06-20 15:22           ` Brice Goglin
2024-06-21  6:23             ` Pawan Gupta
2024-06-27 12:55             ` Ricardo Neri
2024-06-27 12:51           ` Ricardo Neri
2024-06-27 13:22             ` Pawan Gupta
2024-06-27 15:26               ` Ricardo Neri
2024-06-27 16:54               ` Liang, Kan
2024-06-29 11:37               ` Brice Goglin
2024-06-27 12:53       ` Ricardo Neri
2024-06-19 21:22     ` Brice Goglin
2024-06-27 15:22       ` Ricardo Neri
2024-06-27 15:22   ` Ricardo Neri

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=27018603c7ed574451520aeeae405f7b1fcd6c4e.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bp@alien8.de \
    --cc=daniel.sneddon@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=jpoimboe@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=rafael@kernel.org \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.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