From: Frederic Weisbecker <frederic@kernel.org>
To: Anna-Maria Behnsen <anna-maria@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] timer_migration: Spare write when nothing changed
Date: Tue, 25 Jun 2024 00:08:07 +0200 [thread overview]
Message-ID: <ZnnuR8Qp7HeOrSC7@pavilion.home> (raw)
In-Reply-To: <20240624-tmigr-fixes-v2-5-3eb4c0604790@linutronix.de>
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@linutronix.de>
Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
next prev parent reply other threads:[~2024-06-24 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 14:53 [PATCH v2 0/5] timer_migration: Fix two possible races and an improvement Anna-Maria Behnsen
2024-06-24 14:53 ` [PATCH v2 1/5] timer_migration: Do not rely always on group->parent Anna-Maria Behnsen
2024-06-24 20:29 ` Frederic Weisbecker
2024-06-24 14:53 ` [PATCH v2 2/5] timer_migration: Improve tracing Anna-Maria Behnsen
2024-06-24 20:37 ` Frederic Weisbecker
2024-06-24 14:53 ` [PATCH v2 3/5] timer_migration: Split out state update of tmigr_active_up() Anna-Maria Behnsen
2024-06-24 20:42 ` Frederic Weisbecker
2024-06-24 14:53 ` [PATCH v2 4/5] timer_migration: Fix possible race in tmigr_active_up() in setup path Anna-Maria Behnsen
2024-06-24 22:01 ` Frederic Weisbecker
2024-06-24 22:24 ` Frederic Weisbecker
2024-06-24 14:53 ` [PATCH v2 5/5] timer_migration: Spare write when nothing changed Anna-Maria Behnsen
2024-06-24 22:08 ` Frederic Weisbecker [this message]
2024-06-25 0:00 ` [PATCH v2 0/5] timer_migration: Fix two possible races and an improvement Frederic Weisbecker
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=ZnnuR8Qp7HeOrSC7@pavilion.home \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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