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 v3 5/5] x86/amd: Use heterogeneous core topology for identifying boost numerator
Date: Fri, 25 Oct 2024 08:57:46 -0500 [thread overview]
Message-ID: <f1f8c20d-ec13-49d3-ac47-a2fcd4433baf@amd.com> (raw)
In-Reply-To: <20241025135107.GPZxuiS38_s3KWe8xj@fat_crate.local>
On 10/25/2024 08:51, Borislav Petkov wrote:
> On Wed, Oct 23, 2024 at 12:43:57PM -0500, Mario Limonciello wrote:
>> int amd_get_boost_ratio_numerator(unsigned int cpu, u64 *numerator)
>> {
>> + enum x86_topology_cpu_type core_type = get_topology_generic_cpu_type(&cpu_data(cpu));
>> bool prefcore;
>> int ret;
>> + u32 tmp;
>>
>> ret = amd_detect_prefcore(&prefcore);
>> if (ret)
>> @@ -261,6 +263,27 @@ int amd_get_boost_ratio_numerator(unsigned int cpu, u64 *numerator)
>> break;
>> }
>> }
>> +
>
> What's the difference between this case:
>
>> + /* detect if running on heterogeneous design */
>> + switch (core_type) {
>> + case TOPO_CPU_TYPE_UNKNOWN:
> ^^^^^^^^^^^^^^^^^^^^^^^
>
>> + break;
>> + case TOPO_CPU_TYPE_PERFORMANCE:
>> + /* use the max scale for performance cores */
>> + *numerator = CPPC_HIGHEST_PERF_PERFORMANCE;
>> + return 0;
>> + case TOPO_CPU_TYPE_EFFICIENCY:
>> + /* use the highest perf value for efficiency cores */
>> + ret = amd_get_highest_perf(cpu, &tmp);
>> + if (ret)
>> + return ret;
>> + *numerator = tmp;
>> + return 0;
>> + default:
>
> ... and this case and why aren't you warning if TOPO_CPU_TYPE_UNKNOWN?
>
> I think for that you need to check X86_FEATURE_AMD_HETEROGENEOUS_CORES and
> warn if set but still CPU type unknown or?
Yeah; you're right. An earlier version of this behaved differently and
I missed updating this switch/case when using Pawan's updated patch.
After we get Intel feedback on the previous patch I'll drop the
'default' case in the next version and switch it to this:
case TOPO_CPU_TYPE_UNKNOWN:
if (cpu_feature_enabled(X86_FEATURE_AMD_HETEROGENEOUS_CORES))
pr_warn("Undefined core type found for cpu %d\n", cpu);
break;
>
>> + pr_warn("WARNING: Undefined core type %d found\n", core_type);
>> + break;
>> + }
>
prev parent reply other threads:[~2024-10-25 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 17:43 [PATCH v3 0/5] x86 Heterogeneous design identification Mario Limonciello
2024-10-23 17:43 ` [PATCH v3 1/5] x86/cpufeatures: Rename X86_FEATURE_FAST_CPPC to have AMD prefix Mario Limonciello
2024-10-23 17:43 ` [PATCH v3 2/5] x86/cpufeatures: Add feature bits for AMD heterogeneous processor Mario Limonciello
2024-10-23 17:43 ` [PATCH v3 3/5] x86/cpu: Enable SD_ASYM_PACKING for PKG Domain on AMD Processors Mario Limonciello
2024-10-23 17:43 ` [PATCH v3 4/5] x86/cpu: Add CPU type to struct cpuinfo_topology Mario Limonciello
2024-10-25 13:47 ` Borislav Petkov
2024-10-25 16:53 ` Dave Hansen
2024-10-25 17:03 ` Pawan Gupta
2024-10-23 17:43 ` [PATCH v3 5/5] x86/amd: Use heterogeneous core topology for identifying boost numerator Mario Limonciello
2024-10-25 13:51 ` Borislav Petkov
2024-10-25 13:57 ` Mario Limonciello [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=f1f8c20d-ec13-49d3-ac47-a2fcd4433baf@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