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>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>, Perry Yuan <Perry.Yuan@amd.com>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Subject: Re: [PATCH v2] x86/cpu: Enable SD_ASYM_PACKING for PKG domain on systems with AMD preferred cores
Date: Tue, 3 Dec 2024 16:02:29 -0600 [thread overview]
Message-ID: <f71aff95-3aea-4681-9d35-9847b086cc8e@amd.com> (raw)
In-Reply-To: <20241203215454.GJZ09-LmEWPZ502B7R@fat_crate.local>
On 12/3/2024 15:54, Borislav Petkov wrote:
> On Tue, Dec 03, 2024 at 02:11:29PM -0600, Mario Limonciello wrote:
>> For the scheduler to use and prefer AMD preferred core rankings set
>> SD_ASYM_PACKING for x86_die_flags().
>>
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>> ---
>> v2:
>> * Fix c23 compatibility issue reported by LKP
>> ---
>> arch/x86/kernel/smpboot.c | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
>> index b5a8f0891135b..6a38cf3feb1a9 100644
>> --- a/arch/x86/kernel/smpboot.c
>> +++ b/arch/x86/kernel/smpboot.c
>> @@ -62,6 +62,8 @@
>> #include <linux/mc146818rtc.h>
>> #include <linux/acpi.h>
>>
>> +#include <acpi/cppc_acpi.h>
>> +
>> #include <asm/acpi.h>
>> #include <asm/cacheinfo.h>
>> #include <asm/desc.h>
>> @@ -501,6 +503,15 @@ static int x86_die_flags(void)
>> cpu_feature_enabled(X86_FEATURE_AMD_HETEROGENEOUS_CORES))
>> return x86_sched_itmt_flags();
>>
>> + if (boot_cpu_data.x86_vendor == X86_VENDOR_AMD ||
>> + boot_cpu_data.x86_vendor == X86_VENDOR_HYGON) {
>
> You're going to call this on *every* AMD and on Hygon?
>
> So that whole effort with X86_FEATURE_s was for nothing?
>
> What's up?
>
Preferred core classifications are available on "non-heterogenous"
designs for a few generations. There isn't an indication they're
supported which is why amd_detect_prefcore() was made.
That's already called during the boot either way because that is used
to identify the boost numerator. The boolean value it finds is cached,
and the next call will use the cached value. So I don't expect this
change affects boot speed.
next prev parent reply other threads:[~2024-12-03 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 20:11 Mario Limonciello
2024-12-03 20:33 ` Peter Jung
2024-12-03 21:54 ` Borislav Petkov
2024-12-03 22:02 ` Mario Limonciello [this message]
2024-12-03 22:17 ` Borislav Petkov
2024-12-03 22:21 ` 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=f71aff95-3aea-4681-9d35-9847b086cc8e@amd.com \
--to=mario.limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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®