From: Li Chen <me@linux.beauty>
To: 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>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Sohil Mehta <sohil.mehta@intel.com>,
Brian Gerst <brgerst@gmail.com>,
Patryk Wlazlyn <patryk.wlazlyn@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH V2 0/2] x86/smpboot: tidy sched-topology and drop useless SMT level
Date: Tue, 24 Jun 2025 16:55:55 +0800 [thread overview]
Message-ID: <20250624085559.69436-1-me@linux.beauty> (raw)
From: Li Chen <chenl311@chinatelecom.cn>
This two–patch series cleans up sched-domain topology handling and
eliminates hundreds of pointless attach/destroy cycles 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.
changelog:
v2: fix wording issue as suggested by Thomas [1]
[1]: https://www.spinics.net/lists/kernel/msg5732082.html
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(-)
--
2.49.0
next reply other threads:[~2025-06-24 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 8:55 Li Chen [this message]
2025-06-24 8:55 ` [PATCH V2 1/2] x86/smpboot: Decrapify build_sched_topology() Li Chen
2025-06-24 8:55 ` [PATCH V2 2/2] x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled Li Chen
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=20250624085559.69436-1-me@linux.beauty \
--to=me@linux.beauty \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--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®