linux-kernel - Re: [PATCH v2 5/5] timer_migration: Spare write when nothing changed

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: <ZnnuR8Qp7HeOrSC7@pavilion.home>
Date: Tue, 25 Jun 2024 00:08:07 +0200
From: Frederic Weisbecker <frederic@...nel.org>
To: Anna-Maria Behnsen <anna-maria@...utronix.de>
Cc: Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 5/5] timer_migration: Spare write when nothing changed

Le Mon, Jun 24, 2024 at 04:53:57PM +0200, Anna-Maria Behnsen a écrit :
> The wakeup value is written unconditionally in tmigr_cpu_new_timer(). When
> there was no new next timer expiry that needs to be propagated, then the
> value that was read before is written. This is not required.
> 
> Move write to the place where wakeup value could have changed.
> 
> Signed-off-by: Anna-Maria Behnsen <anna-maria@...utronix.de>

Reviewed-by: Frederic Weisbecker <frederic@...nel.org>