From: Michael Ellerman <mpe@ellerman.id.au>
To: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT pull] smp/core for v6.6-rc1
Date: Tue, 05 Sep 2023 12:33:03 +1000 [thread overview]
Message-ID: <87cyyxic2o.fsf@mail.lhotse> (raw)
In-Reply-To: <169322654880.420889.9261217338657613439.tglx@xen13.tec.linutronix.de>
Thomas Gleixner <tglx@linutronix.de> writes:
> Linus,
>
> please pull the latest smp/core branch from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-core-2023-08-28
>
> up to: e0a99a839f04: Documentation: core-api/cpuhotplug: Fix state names
>
>
> Updates for the CPU hotplug core:
>
> - Support partial SMT enablement.
>
> So far the sysfs SMT control only allows to toggle between SMT on and
> off. That's sufficient for x86 which usually has at max two threads
> except for the Xeon PHI platform which has four threads per core.
>
> Though PowerPC has up to 16 threads per core and so far it's only
The threads per core value comes from firmware, so in theory it can be
anything.
But in practice the max on any existing system is 8 threads per core.
cheers
next prev parent reply other threads:[~2023-09-05 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 13:01 [GIT pull] core/entry for v6.6-rc1 Thomas Gleixner
2023-08-28 13:01 ` [GIT pull] irq/core " Thomas Gleixner
2023-08-28 22:15 ` pr-tracker-bot
2023-08-28 13:01 ` [GIT pull] smp/core " Thomas Gleixner
2023-08-28 22:15 ` pr-tracker-bot
2023-09-05 2:33 ` Michael Ellerman [this message]
2023-08-28 21:07 ` [GIT pull] core/entry " Linus Torvalds
2023-08-28 21:32 ` Linus Torvalds
2023-08-28 21:38 ` Thomas Gleixner
2023-08-28 22:15 ` pr-tracker-bot
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=87cyyxic2o.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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