From: Usama Arif <usamaarif642@gmail.com>
To: Frederic Weisbecker <frederic@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
vlad.wing@gmail.com, rcu@vger.kernel.org, boqun.feng@gmail.com,
joel@joelfernandes.org, neeraj.upadhyay@amd.com,
urezki@gmail.com, qiang.zhang1211@gmail.com,
Cheng-Jui.Wang@mediatek.com, leitao@debian.org,
kernel-team@meta.com, paulmck@kernel.org,
Anna-Maria Behnsen <anna-maria@linutronix.de>
Subject: Re: [PATCH 2/3 v2] rcu: Remove swake_up_one_online() bandaid
Date: Mon, 30 Dec 2024 13:46:05 +0000 [thread overview]
Message-ID: <c906fb34-7b63-4829-bf2d-1ee0ae85d4e2@gmail.com> (raw)
In-Reply-To: <20241226233052.145450-3-frederic@kernel.org>
On 26/12/2024 23:30, Frederic Weisbecker wrote:
> It's now ok to perform a wake-up from an offline CPU because the
> resulting armed scheduler bandwidth hrtimers are now correctly targeted
> by hrtimer infrastructure.
>
> Remove the obsolete hackerry.
>
> Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Reviewed-by: Usama Arif <usamaarif642@gmail.com>
next prev parent reply other threads:[~2024-12-30 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 23:30 [PATCH 0/3 v2] hrtimer: Fix timers queued locally from offline CPUs Frederic Weisbecker
2024-12-26 23:30 ` [PATCH 1/3 v2] hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING Frederic Weisbecker
2024-12-30 12:19 ` Usama Arif
2024-12-26 23:30 ` [PATCH 2/3 v2] rcu: Remove swake_up_one_online() bandaid Frederic Weisbecker
2024-12-30 13:46 ` Usama Arif [this message]
2024-12-26 23:30 ` [PATCH 3/3 v2] Revert "rcu/nocb: Fix rcuog wake-up from offline softirq" Frederic Weisbecker
2024-12-30 13:47 ` Usama Arif
2025-01-01 4:56 ` [PATCH 0/3 v2] hrtimer: Fix timers queued locally from offline CPUs Paul E. McKenney
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=c906fb34-7b63-4829-bf2d-1ee0ae85d4e2@gmail.com \
--to=usamaarif642@gmail.com \
--cc=Cheng-Jui.Wang@mediatek.com \
--cc=anna-maria@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@amd.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=vlad.wing@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.