From: Mario Limonciello <mario.limonciello@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Gautham R . Shenoy" <gautham.shenoy@amd.com>,
Perry Yuan <perry.yuan@amd.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Peter Zijlstra <peterz@infradead.org>,
Li RongQing <lirongqing@baidu.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
"open list:ACPI" <linux-acpi@vger.kernel.org>,
"open list:AMD PSTATE DRIVER" <linux-pm@vger.kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Subject: Re: [PATCH v2 4/5] x86/cpu: Add CPU type to struct cpuinfo_topology
Date: Tue, 22 Oct 2024 10:41:13 -0500 [thread overview]
Message-ID: <29c7b5b9-3a27-4b3c-85af-e08287944a00@amd.com> (raw)
In-Reply-To: <20241022120336.GCZxeUmHL5p6chpt0m@fat_crate.local>
On 10/22/2024 07:03, Borislav Petkov wrote:
> On Tue, Oct 22, 2024 at 01:57:20PM +0200, Borislav Petkov wrote:
>> diff --git a/arch/x86/kernel/cpu/topology_common.c b/arch/x86/kernel/cpu/topology_common.c
>> index 9a6069e7133c..38220b64c6b3 100644
>> --- a/arch/x86/kernel/cpu/topology_common.c
>> +++ b/arch/x86/kernel/cpu/topology_common.c
>> @@ -27,6 +27,23 @@ void topology_set_dom(struct topo_scan *tscan, enum x86_topology_domains dom,
>> }
>> }
>>
>> +const char *get_topology_cpu_type_name(struct cpuinfo_x86 *c)
>> +{
>> + enum x86_topology_cpu_type type;
>> +
>> + if (c->x86_vendor == X86_VENDOR_INTEL)
>> + type = get_intel_cpu_type(c);
>> + if (c->x86_vendor == X86_VENDOR_AMD)
>> + type = get_amd_cpu_type(c);
>> +
>> + if (type == TOPO_CPU_TYPE_PERFORMANCE)
>> + return "performance";
>> + else if (type == TOPO_CPU_TYPE_EFFICIENCY)
>> + return "efficiency";
>> + else
>> + return "unknown";
>> +}
>
> I guess you still need topology_cpu_type() in your next patch but that's easy
> - you simply call it in get_topology_cpu_type_name().
>
> The point being debugfs will dump the name of the core type and not some magic
> number which no one knows.
Yeah; makes sense. I'll pull your suggestions in.
next prev parent reply other threads:[~2024-10-22 15:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 3:46 [PATCH v2 0/5] x86 Heterogeneous design identification Mario Limonciello
2024-10-22 3:46 ` [PATCH v2 1/5] x86/cpufeatures: Rename X86_FEATURE_FAST_CPPC to have AMD prefix Mario Limonciello
2024-10-22 3:46 ` [PATCH v2 2/5] x86/cpufeatures: Add feature bits for AMD heterogeneous processor Mario Limonciello
2024-10-22 3:46 ` [PATCH v2 3/5] x86/cpu: Enable SD_ASYM_PACKING for PKG Domain on AMD Processors Mario Limonciello
2024-10-22 9:20 ` Gautham R. Shenoy
2024-10-22 3:46 ` [PATCH v2 4/5] x86/cpu: Add CPU type to struct cpuinfo_topology Mario Limonciello
2024-10-22 11:57 ` Borislav Petkov
2024-10-22 12:03 ` Borislav Petkov
2024-10-22 15:41 ` Mario Limonciello [this message]
2024-10-22 16:03 ` Dave Hansen
2024-10-22 16:13 ` Mario Limonciello
2024-10-22 17:09 ` Dave Hansen
2024-10-23 3:58 ` Pawan Gupta
2024-10-23 4:40 ` Pawan Gupta
2024-10-23 15:59 ` Borislav Petkov
2024-10-22 3:46 ` [PATCH v2 5/5] x86/amd: Use heterogeneous core topology for identifying boost numerator Mario Limonciello
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=29c7b5b9-3a27-4b3c-85af-e08287944a00@amd.com \
--to=mario.limonciello@amd.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=gautham.shenoy@amd.com \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=perry.yuan@amd.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--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®