From: Laurent Dufour <ldufour@linux.ibm.com>
To: Sachin Sant <sachinp@linux.ibm.com>
Cc: linux-arch@vger.kernel.org, dave.hansen@linux.intel.com,
open list <linux-kernel@vger.kernel.org>,
npiggin@gmail.com, Ingo Molnar <mingo@redhat.com>,
bp@alien8.de, tglx@linutronix.de,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v3 0/9] Introduce SMT level and add PowerPC support
Date: Fri, 30 Jun 2023 15:41:24 +0200 [thread overview]
Message-ID: <beda2b05-db6f-54a8-719b-7f4888647791@linux.ibm.com> (raw)
In-Reply-To: <58662E98-81B0-4553-9A75-4CA033720BE3@linux.ibm.com>
Le 30/06/2023 à 15:32, Sachin Sant a écrit :
>
>
>> On 29-Jun-2023, at 8:01 PM, Laurent Dufour <ldufour@linux.ibm.com> wrote:
>>
>> I'm taking over the series Michael sent previously [1] which is smartly
>> reviewing the initial series I sent [2]. This series is addressing the
>> comments sent by Thomas and me on the Michael's one.
>>
>> Here is a short introduction to the issue this series is addressing:
>>
>> When a new CPU is added, the kernel is activating all its threads. This
>> leads to weird, but functional, result when adding CPU on a SMT 4 system
>> for instance.
>>
>> Here the newly added CPU 1 has 8 threads while the other one has 4 threads
>> active (system has been booted with the 'smt-enabled=4' kernel option):
>>
>> ltcden3-lp12:~ # ppc64_cpu --info
>> Core 0: 0* 1* 2* 3* 4 5 6 7
>> Core 1: 8* 9* 10* 11* 12* 13* 14* 15*
>>
>> This mixed SMT level may confused end users and/or some applications.
>>
>> There is no SMT level recorded in the kernel (common code), neither in user
>> space, as far as I know. Such a level is helpful when adding new CPU or
>> when optimizing the energy efficiency (when reactivating CPUs).
>>
>> When SMP and HOTPLUG_SMT are defined, this series is adding a new SMT level
>> (cpu_smt_num_threads) and few callbacks allowing the architecture code to
>> fine control this value, setting a max and a "at boot" level, and
>> controling whether a thread should be onlined or not.
>>
>> v3:
>> Fix a build error in the patch 6/9
>
> Successfully tested the V3 version on a Power10 LPAR. Add/remove of
> processor core worked correctly, preserving the SMT level (on a kernel
> booted with smt-enabled= parameter)
>
> Laurent (Thanks!) also provided a patch to update the ppc64_cpu &
> lparstat utility. With patched ppc64_cpu utility verified that SMT level
> changed at runtime was preserved across processor core add (on
> a kernel booted without smt-enabled= parameter)
>
> Based on these test results
>
> Tested-by: Sachin Sant <sachinp@linux.ibm.com>
Thanks a lot, Sachin!
Once this series is accepted, I'll send the series to update ppc64_cpu.
next prev parent reply other threads:[~2023-06-30 13:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 14:31 [PATCH v3 0/9] Introduce SMT level and add PowerPC support Laurent Dufour
2023-06-29 14:31 ` [PATCH v3 1/9] cpu/SMT: Move SMT prototypes into cpu_smt.h Laurent Dufour
2023-06-29 14:31 ` [PATCH v3 2/9] cpu/SMT: Move smt/control simple exit cases earlier Laurent Dufour
2023-06-29 14:31 ` [PATCH v3 3/9] cpu/SMT: Store the current/max number of threads Laurent Dufour
2023-07-05 3:05 ` Zhang, Rui
2023-07-05 11:58 ` Laurent Dufour
2023-06-29 14:31 ` [PATCH v3 4/9] cpu/SMT: Remove topology_smt_supported() Laurent Dufour
2023-06-29 14:31 ` [PATCH v3 5/9] cpu/SMT: Create topology_smt_thread_allowed() Laurent Dufour
2023-06-29 14:31 ` [PATCH v3 6/9] cpu/SMT: Allow enabling partial SMT states via sysfs Laurent Dufour
2023-07-05 3:14 ` Zhang, Rui
2023-07-05 11:57 ` Laurent Dufour
2023-06-29 14:31 ` [PATCH v3 7/9] powerpc/pseries: Initialise CPU hotplug callbacks earlier Laurent Dufour
2023-06-29 14:31 ` [PATCH v3 8/9] powerpc: Add HOTPLUG_SMT support Laurent Dufour
2023-06-30 15:19 ` Laurent Dufour
2023-06-29 14:31 ` [PATCH v3 9/9] powerpc/pseries: Honour current SMT state when DLPAR onlining CPUs Laurent Dufour
2023-06-30 13:32 ` [PATCH v3 0/9] Introduce SMT level and add PowerPC support Sachin Sant
2023-06-30 13:41 ` Laurent Dufour [this message]
2023-07-05 3:04 ` Zhang, Rui
2023-07-05 11:53 ` Laurent Dufour
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=beda2b05-db6f-54a8-719b-7f4888647791@linux.ibm.com \
--to=ldufour@linux.ibm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=npiggin@gmail.com \
--cc=sachinp@linux.ibm.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).