mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Li Chen <me@linux.beauty>
Cc: 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>,
	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, Li Chen <chenl311@chinatelecom.cn>
Subject: Re: [PATCH v3 1/2] x86/smpboot: Decrapify build_sched_topology()
Date: Wed, 25 Jun 2025 10:28:19 +0200	[thread overview]
Message-ID: <20250625082819.GZ1613200@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250625034552.42365-2-me@linux.beauty>

On Wed, Jun 25, 2025 at 11:45:49AM +0800, Li Chen wrote:
> From: Thomas Gleixner <tglx@linutronix.de>
> 
> The #ifdeffery and the initializers in build_sched_topology() are just
> disgusting. The SCHED_SMT #ifdef is also pointless because SCHED_SMT is
> unconditionally enabled when SMP is enabled.

On x86, but not across all archs. Yes this is x86 code, but how is one
supposed to keep all that nonsense straight in their head ;-)

> Statically initialize the domain levels in the topology array and let
> build_sched_topology() invalidate the package domain level when NUMA in
> package is available.
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
>  arch/x86/kernel/smpboot.c | 45 +++++++++++++++------------------------
>  1 file changed, 17 insertions(+), 28 deletions(-)
> 
> diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
> index fc78c2325fd29..7d202f9785362 100644
> --- a/arch/x86/kernel/smpboot.c
> +++ b/arch/x86/kernel/smpboot.c
> @@ -478,43 +478,32 @@ static int x86_cluster_flags(void)
>   */
>  static bool x86_has_numa_in_package;
>  
> -static struct sched_domain_topology_level x86_topology[6];
> +#define DOMAIN(maskfn, flagsfn, dname) { .mask = maskfn, .sd_flags = flagsfn, .name = #dname }
>  
> -static void __init build_sched_topology(void)
> -{
> -	int i = 0;
> -
> -#ifdef CONFIG_SCHED_SMT
> -	x86_topology[i++] = (struct sched_domain_topology_level){
> -		cpu_smt_mask, cpu_smt_flags, SD_INIT_NAME(SMT)
> -	};
> -#endif
> +static struct sched_domain_topology_level x86_topology[] = {
> +	DOMAIN(cpu_smt_mask, cpu_smt_flags, SMT),
>  #ifdef CONFIG_SCHED_CLUSTER
> -	x86_topology[i++] = (struct sched_domain_topology_level){
> -		cpu_clustergroup_mask, x86_cluster_flags, SD_INIT_NAME(CLS)
> -	};
> +	DOMAIN(cpu_clustergroup_mask, x86_cluster_flags, CLS),
>  #endif
>  #ifdef CONFIG_SCHED_MC
> -	x86_topology[i++] = (struct sched_domain_topology_level){
> -		cpu_coregroup_mask, x86_core_flags, SD_INIT_NAME(MC)
> -	};
> +	DOMAIN(cpu_coregroup_mask, x86_core_flags, MC),
>  #endif
> -	/*
> -	 * When there is NUMA topology inside the package skip the PKG domain
> -	 * since the NUMA domains will auto-magically create the right spanning
> -	 * domains based on the SLIT.
> -	 */
> -	if (!x86_has_numa_in_package) {
> -		x86_topology[i++] = (struct sched_domain_topology_level){
> -			cpu_cpu_mask, x86_sched_itmt_flags, SD_INIT_NAME(PKG)
> -		};
> -	}
> +	DOMAIN(cpu_cpu_mask, x86_sched_itmt_flags, PKG),
> +	{ NULL },
> +};
>  
> +static void __init build_sched_topology(void)
> +{
>  	/*
> -	 * There must be one trailing NULL entry left.
> +	 * When there is NUMA topology inside the package invalidate the
> +	 * PKG domain since the NUMA domains will auto-magically create the
> +	 * right spanning domains based on the SLIT.
>  	 */
> -	BUG_ON(i >= ARRAY_SIZE(x86_topology)-1);
> +	if (x86_has_numa_in_package) {
> +		unsigned int pkgdom = ARRAY_SIZE(x86_topology) - 2;
>  
> +		memset(&x86_topology[pkgdom], 0, sizeof(x86_topology[pkgdom]));
> +	}
>  	set_sched_topology(x86_topology);
>  }

Urgh, this patch is doing at least 4 things and nigh on unreadable
because of that.

 - introduces DOMAIN() helper
 - drops (the now pointless) SD_INIT_NAME() helper
 - drops CONFIG_SCHED_SMT (x86 special)
 - moves to static initialize and truncate



  reply	other threads:[~2025-06-25  8:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25  3:45 [PATCH v3 0/2] x86/smpboot: tidy sched-topology and drop useless SMT level 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 [this message]
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 ` [PATCH v3 0/2] x86/smpboot: tidy sched-topology and drop useless SMT level K Prateek Nayak

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=20250625082819.GZ1613200@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=chenl311@chinatelecom.cn \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@linux.beauty \
    --cc=mingo@redhat.com \
    --cc=patryk.wlazlyn@linux.intel.com \
    --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®