All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Michael Ellerman <mpe@ellerman.id.au>, linux-kernel@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org,
	ldufour@linux.ibm.com, bp@alien8.de, dave.hansen@linux.intel.com,
	mingo@redhat.com, x86@kernel.org
Subject: Re: [PATCH 4/9] cpu/SMT: Create topology_smt_threads_supported()
Date: Sun, 11 Jun 2023 00:15:52 +0200	[thread overview]
Message-ID: <878rcr7ylj.ffs@tglx> (raw)
In-Reply-To: <20230524155630.794584-4-mpe@ellerman.id.au>

On Thu, May 25 2023 at 01:56, Michael Ellerman wrote:
> +/**
> + * topology_smt_threads_supported - Check if the given number of SMT threads
> + *				    is supported.
> + *
> + * @threads:	The number of SMT threads.
> + */
> +bool topology_smt_threads_supported(unsigned int threads)
> +{
> +	// Only support a single thread or all threads.
> +	return threads == 1 || threads == smp_num_siblings;
> +}

You can make that a simple core function when cpu_smt_*_threads is
consistent along the lines of my previous reply.

static bool cpu_smt_num_threads_valid(unsigned int threads)
{
        if (IS_ENABLED(CONFIG_SMT_NUM_THREADS_DYNAMIC))
		return threads >= 1 && threads <= cpu_smt_max_threads;
        return threads == 1 || threads == cpu_smt_max_threads;
}

Or something like that.

Thanks,

        tglx

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Michael Ellerman <mpe@ellerman.id.au>, linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org, x86@kernel.org,
	dave.hansen@linux.intel.com, mingo@redhat.com, bp@alien8.de,
	ldufour@linux.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 4/9] cpu/SMT: Create topology_smt_threads_supported()
Date: Sun, 11 Jun 2023 00:15:52 +0200	[thread overview]
Message-ID: <878rcr7ylj.ffs@tglx> (raw)
In-Reply-To: <20230524155630.794584-4-mpe@ellerman.id.au>

On Thu, May 25 2023 at 01:56, Michael Ellerman wrote:
> +/**
> + * topology_smt_threads_supported - Check if the given number of SMT threads
> + *				    is supported.
> + *
> + * @threads:	The number of SMT threads.
> + */
> +bool topology_smt_threads_supported(unsigned int threads)
> +{
> +	// Only support a single thread or all threads.
> +	return threads == 1 || threads == smp_num_siblings;
> +}

You can make that a simple core function when cpu_smt_*_threads is
consistent along the lines of my previous reply.

static bool cpu_smt_num_threads_valid(unsigned int threads)
{
        if (IS_ENABLED(CONFIG_SMT_NUM_THREADS_DYNAMIC))
		return threads >= 1 && threads <= cpu_smt_max_threads;
        return threads == 1 || threads == cpu_smt_max_threads;
}

Or something like that.

Thanks,

        tglx

  reply	other threads:[~2023-06-10 22:15 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 15:56 [PATCH 1/9] cpu/SMT: Move SMT prototypes into cpu_smt.h Michael Ellerman
2023-05-24 15:56 ` Michael Ellerman
2023-05-24 15:56 ` [PATCH 2/9] cpu/SMT: Move smt/control simple exit cases earlier Michael Ellerman
2023-05-24 15:56   ` Michael Ellerman
2023-05-24 15:56 ` [PATCH 3/9] cpu/SMT: Store the current/max number of threads Michael Ellerman
2023-05-24 15:56   ` Michael Ellerman
2023-06-10 21:26   ` Thomas Gleixner
2023-06-10 21:26     ` Thomas Gleixner
2023-06-10 22:08     ` Thomas Gleixner
2023-06-10 22:08       ` Thomas Gleixner
2023-06-13 17:16     ` Laurent Dufour
2023-06-13 17:16       ` Laurent Dufour
2023-06-13 18:53       ` Thomas Gleixner
2023-06-13 18:53         ` Thomas Gleixner
2023-06-14 12:27         ` Laurent Dufour
2023-06-14 12:27           ` Laurent Dufour
2023-05-24 15:56 ` [PATCH 4/9] cpu/SMT: Create topology_smt_threads_supported() Michael Ellerman
2023-05-24 15:56   ` Michael Ellerman
2023-06-10 22:15   ` Thomas Gleixner [this message]
2023-06-10 22:15     ` Thomas Gleixner
2023-05-24 15:56 ` [PATCH 5/9] cpu/SMT: Create topology_smt_thread_allowed() Michael Ellerman
2023-05-24 15:56   ` Michael Ellerman
2023-06-10 22:35   ` Thomas Gleixner
2023-06-10 22:35     ` Thomas Gleixner
2023-05-24 15:56 ` [PATCH 6/9] cpu/SMT: Allow enabling partial SMT states via sysfs Michael Ellerman
2023-05-24 15:56   ` Michael Ellerman
2023-06-10 20:09   ` Thomas Gleixner
2023-06-10 20:09     ` Thomas Gleixner
2023-06-10 20:13     ` Thomas Gleixner
2023-06-10 20:13       ` Thomas Gleixner
2023-05-24 15:56 ` [PATCH 7/9] powerpc/pseries: Initialise CPU hotplug callbacks earlier Michael Ellerman
2023-05-24 15:56   ` Michael Ellerman
2023-05-24 15:56 ` [PATCH 8/9] powerpc: Add HOTPLUG_SMT support Michael Ellerman
2023-05-24 15:56   ` Michael Ellerman
2023-06-01 13:27   ` Laurent Dufour
2023-06-01 13:27     ` Laurent Dufour
2023-06-01 16:19     ` Laurent Dufour
2023-06-01 16:19       ` Laurent Dufour
2023-06-10 21:10       ` Thomas Gleixner
2023-06-10 21:10         ` Thomas Gleixner
2023-06-12 15:20         ` Laurent Dufour
2023-06-12 15:20           ` Laurent Dufour
2023-06-12 16:34           ` Thomas Gleixner
2023-06-12 16:34             ` Thomas Gleixner
2023-05-24 15:56 ` [PATCH 9/9] powerpc/pseries: Honour current SMT state when DLPAR onlining CPUs Michael Ellerman
2023-05-24 15:56   ` Michael Ellerman

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=878rcr7ylj.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=ldufour@linux.ibm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.