mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, 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>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	"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>,
	Brice Goglin <brice.goglin@gmail.com>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Perry Yuan <Perry.Yuan@amd.com>,
	Dapeng Mi <dapeng1.mi@linux.intel.com>
Subject: Re: [PATCH v4 02/10] x86/cpu/topology: Add CPU type to struct cpuinfo_topology
Date: Mon, 21 Oct 2024 15:38:06 +0200	[thread overview]
Message-ID: <9534B53F-7B91-4525-97DC-889EC3836658@alien8.de> (raw)
In-Reply-To: <20241018203053.2x6oyws3dkxfw6rm@desk>

On October 18, 2024 10:30:53 PM GMT+02:00, Pawan Gupta <pawan.kumar.gupta@linux.intel.com> wrote:
>I will drop "core", but can we keep "native"? "native" is used in SDM to
>define this field. Also model_id could be confused with model number.
>
>  From Intel SDM Vol. 2A:
>
>  Bits 23-00: Native model ID of the core. The core-type and native model
>  ID can be used to uniquely identify the microarchitecture of the core.
>  This native model ID is not unique across core types, and not related to
>  the model ID reported in CPUID leaf 01H, and does not identify the SOC.

I'm still not clear on what "native" is supposed to mean here?

The core is born this way and then it changes... so this is its native model ID? Weird...

>Yes, topo.hw_cpu_type is initialized to TOPO_HW_CPU_TYPE_UNKNOWN. We should
>not ideally need the vendor check at all. As long as topo.hw_cpu_type has
>the core type, returning it should be enough here. For Intel hw_cpu_type
>also has the native_model_id, that is why we need the vendor check.
>
>If AMD or other vendors have similar use case, it makes sense to add the
>explicit vendor check. Please let me know if thats the likely case.

Yes, it either needs to be vendor-agnostic or you need to accommodate all vendors. Former sounds cleaner...

-- 
Sent from a small device: formatting sucks and brevity is inevitable.

  reply	other threads:[~2024-10-21 13:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 14:47 [PATCH v4 00/10] Add CPU-type to topology Pawan Gupta
2024-09-30 14:47 ` [PATCH v4 01/10] x86/cpu: Prepend 0x to the hex values in cpu_debug_show() Pawan Gupta
2024-09-30 14:47 ` [PATCH v4 02/10] x86/cpu/topology: Add CPU type to struct cpuinfo_topology Pawan Gupta
2024-10-18 16:19   ` Borislav Petkov
2024-10-18 20:30     ` Pawan Gupta
2024-10-21 13:38       ` Borislav Petkov [this message]
2024-10-21 16:36         ` Pawan Gupta
2024-10-21 17:13           ` Luck, Tony
2024-10-21 17:45             ` Borislav Petkov
2024-10-21 17:59               ` Luck, Tony
2024-10-18 16:28   ` Mario Limonciello
2024-10-18 21:11     ` Pawan Gupta
2024-10-22 14:42       ` Mario Limonciello
2024-10-23  5:12         ` Pawan Gupta
2024-09-30 14:47 ` [PATCH v4 03/10] cpufreq: intel_pstate: Use topology_hw_cpu_type() Pawan Gupta
2024-09-30 14:47 ` [PATCH v4 04/10] perf/x86/intel: " Pawan Gupta
2024-10-21 13:54   ` Liang, Kan
2024-10-21 16:17     ` Pawan Gupta
2024-09-30 14:47 ` [PATCH v4 05/10] x86/cpu: Remove get_this_hybrid_cpu_type() Pawan Gupta
2024-09-30 14:47 ` [PATCH v4 06/10] x86/cpu: Name CPU matching macro more generically (and shorten) Pawan Gupta
2024-09-30 14:47 ` [PATCH v4 07/10] x86/cpu: Add cpu_type to struct x86_cpu_id Pawan Gupta
2024-09-30 14:48 ` [PATCH v4 08/10] x86/cpu: Update x86_match_cpu() to also use cpu-type Pawan Gupta
2024-09-30 14:48 ` [PATCH v4 09/10] x86/bugs: Declutter vulnerable CPU list Pawan Gupta
2024-09-30 14:48 ` [PATCH v4 10/10] x86/rfds: Exclude P-only parts from the RFDS affected list Pawan Gupta
2024-09-30 15:12 ` [PATCH v4 00/10] Add CPU-type to topology Dave Hansen
2024-09-30 22:28   ` Pawan Gupta

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=9534B53F-7B91-4525-97DC-889EC3836658@alien8.de \
    --to=bp@alien8.de \
    --cc=Perry.Yuan@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=brice.goglin@gmail.com \
    --cc=daniel.sneddon@linux.intel.com \
    --cc=dapeng1.mi@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=mario.limonciello@amd.com \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=rafael@kernel.org \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=srinivas.pandruvada@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

all inboxes | Powered by JetHome®