linux-kernel - Re: [PATCH v15 2/7] timers: Add the available mask in timer migration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87v7j6kocf.ffs@tglx>
Date: Wed, 19 Nov 2025 16:56:48 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Gabriele Monaco <gmonaco@...hat.com>, linux-kernel@...r.kernel.org,
 Anna-Maria Behnsen <anna-maria@...utronix.de>, Frederic Weisbecker
 <frederic@...nel.org>, Waiman Long <longman@...hat.com>
Cc: Gabriele Monaco <gmonaco@...hat.com>
Subject: Re: [PATCH v15 2/7] timers: Add the available mask in timer migration

On Thu, Nov 13 2025 at 09:33, Gabriele Monaco wrote:

Can we please consistently have 'timers/migration:' as prefix like the
other existing commits for this series? 

That allows to write this subject line in a coherent way:

     timers/migration: Provide and use cpumask for available CPUs

or something like that.

Why did I waste time for documenting all of this?

   https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#patch-subject

   "‘git log path/to/file’ should give you a reasonable hint in most cases."

Is it really that hard?

> Keep track of the CPUs available for timer migration in a cpumask. This
> prepares the ground to generalise the concept of unavailable CPUs.
>
> Reviewed-by: Frederic Weisbecker <frederic@...nel.org>
> Signed-off-by: Gabriele Monaco <gmonaco@...hat.com>

Aside of the nit above:

Reviewed-by: Thomas Gleixner <tglx@...utronix.de>