From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Li Chen <me@linux.beauty>, 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, "H . Peter Anvin" <hpa@zytor.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Sohil Mehta <sohil.mehta@intel.com>,
Brian Gerst <brgerst@gmail.com>,
Patryk Wlazlyn <patryk.wlazlyn@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] x86/smpboot: tidy sched-topology and drop useless SMT level
Date: Wed, 25 Jun 2025 11:20:39 +0530 [thread overview]
Message-ID: <4e2afb04-7317-4689-95c0-dfa82311f256@amd.com> (raw)
In-Reply-To: <20250625034552.42365-1-me@linux.beauty>
Hello Li,
On 6/25/2025 9:15 AM, Li Chen wrote:
> From: Li Chen <chenl311@chinatelecom.cn>
>
> This two–patch series cleans up sched-domain topology handling and
> eliminates hundreds of pointless attach/destroy cycles for large
> machines when SMT is not available.
>
> Patch 1 (from Thomas, unchanged) gets rid of the #ifdef maze in
> build_sched_topology() by statically initialising the topology array.
>
> Patch 2 (mine) is a follow-up that simply memmoves the array when
> cpu_smt_num_threads <= 1, so the SMT level never gets created and
> immediately torn down again.
>
> Tested on Qemu.
I think there is a simpler approach to Patch 2 but other than that
I gave this series a spin during my review with different topology
on QEMU and didn't find any surprises. I tested with and without
the "threads" parameter to "-smp" and also with "nosmt" kernel
cmdline and everything seemed to be in order. Feel free to add:
Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
>
> changelog:
> v2: fix wording issue as suggested by Thomas [1]
> v3: remove pointless memset and adjust PKG index accordingly, as
> suggested by Thomas [2], and refine some other wording issues.
>
> [1]: https://lore.kernel.org/all/87msa2r018.ffs@tglx/
> [2]: https://lore.kernel.org/all/875xglntx1.ffs@tglx/
>
> Li Chen (1):
> x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled
>
> Thomas Gleixner (1):
> x86/smpboot: Decrapify build_sched_topology()
>
> arch/x86/kernel/smpboot.c | 59 +++++++++++++++++++++------------------
> 1 file changed, 32 insertions(+), 27 deletions(-)
>
--
Thanks and Regards,
Prateek
prev parent reply other threads:[~2025-06-25 5:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 3:45 Li Chen
2025-06-25 3:45 ` [PATCH v3 1/2] x86/smpboot: Decrapify build_sched_topology() Li Chen
2025-06-25 8:28 ` Peter Zijlstra
2025-06-30 0:21 ` Li Chen
2025-06-30 12:56 ` Thomas Gleixner
2025-06-25 3:45 ` [PATCH v3 2/2] x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled Li Chen
2025-06-25 5:45 ` K Prateek Nayak
2025-06-25 8:30 ` Peter Zijlstra
2025-06-30 0:39 ` Li Chen
2025-06-25 8:29 ` Peter Zijlstra
2025-06-30 0:29 ` Li Chen
2025-06-25 5:50 ` K Prateek Nayak [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=4e2afb04-7317-4689-95c0-dfa82311f256@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@linux.beauty \
--cc=mingo@redhat.com \
--cc=patryk.wlazlyn@linux.intel.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sohil.mehta@intel.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®