From: Thomas Gleixner <tglx@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>, Daniel Lezcano
 <daniel.lezcano@oss.qualcomm.com>
Cc: rafael@kernel.org, peterz@infradead.org, Heiko Stuebner
 <heiko@sntech.de>, "moderated list:ARM/Rockchip SoC support"
 <linux-arm-kernel@lists.infradead.org>, "open list:ARM/Rockchip SoC
 support" <linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH 0/2] powercap: idle_inject: Create threads on demand
In-Reply-To: <20261105105805.a6d1b38585290ab73597aa6b@linux-foundation.org>
References: <cover.1793660202.git.daniel.lezcano@oss.qualcomm.com>
 <493b853d-fe45-4058-914b-a9ee684701db@oss.qualcomm.com>
 <20261105105805.a6d1b38585290ab73597aa6b@linux-foundation.org>
Date: Wed, 11 Nov 2026 01:21:36 +0100
Message-ID: <87bj7wtdyn.ffs@fw13>
MIME-Version: 1.0
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Linux-rockchip" <linux-rockchip-bounces@lists.infradead.org>

On Thu, Nov 05 2026 at 10:58, Andrew Morton wrote:
> On Thu, 5 Nov 2026 19:46:13 +0100 Daniel Lezcano <daniel.lezcano@oss.qualcomm.com> wrote:
>
>> On 11/3/26 00:09, Daniel Lezcano wrote:
>> > Idle injection currently registers per-CPU kernel threads during early
>> > initialization, including on CPUs for which no idle injection device
>> > will be registered.
>> > 
>> > This series makes thread creation follow the lifetime and CPU mask of
>> > each idle injection device.
>> > 
>> > The first patch adds an optional CPU mask to smpboot thread descriptors.
>> > The mask restricts thread creation, CPU hotplug handling and teardown,
>> > while preserving the existing behavior for descriptors without a mask.
>> > 
>> > The second patch uses this support to register idle injection threads
>> > when a device registers and destroy them when it unregisters. CPU
>> > ownership claims, registration rollback and thread teardown are
>> > serialized to prevent overlapping registrations from sharing threads.
>> > 
>> > Validation includes W=1 builds of the affected objects, whitespace
>> > checks and static review of the teardown locking paths. Concurrent
>> > registration and CPU hotplug runtime testing remains outstanding.
>> > 
>> > The series was tested on Rockchip RK3588.
>> 
>> One thing not specified in this cover is which tree these changes have 
>> to go through ?
>
> I'd volunteer Rafael's, after peterz/tglx review.
>
> Please!  Removing one kernel thread per cpu makes the world a better
> place.

I'll look at it in the next days with brain awake...

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip