[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a5x77yye.ffs@tglx>
Date: Sun, 11 Jun 2023 00:08:09 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Michael Ellerman <mpe@...erman.id.au>, linux-kernel@...r.kernel.org
Cc: linuxppc-dev@...ts.ozlabs.org, linux-arch@...r.kernel.org,
ldufour@...ux.ibm.com, bp@...en8.de, dave.hansen@...ux.intel.com,
mingo@...hat.com, x86@...nel.org
Subject: Re: [PATCH 3/9] cpu/SMT: Store the current/max number of threads
On Sat, Jun 10 2023 at 23:26, Thomas Gleixner wrote:
> On Thu, May 25 2023 at 01:56, Michael Ellerman wrote:
> /*
> * The decision whether SMT is supported can only be done after the full
> * CPU identification. Called from architecture code.
> */
> -void __init cpu_smt_check_topology(void)
> +void __init cpu_smt_set_num_threads(unsigned int max_threads, unsigned int num_threads)
> {
> - if (!topology_smt_supported())
> + if (max_threads == 1)
Which makes topology_smt_supported() redundant, i.e. it can be removed.
Thanks,
tglx
Powered by blists - more mailing lists