From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Yonghong Song <yonghong.song@linux.dev>
Cc: paulmck@kernel.org, Steven Rostedt <rostedt@goodmis.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the rcu tree with the ftrace tree
Date: Tue, 18 Nov 2025 08:35:08 +0100 [thread overview]
Message-ID: <20251118073508.JdhVECQD@linutronix.de> (raw)
In-Reply-To: <5d6033df-b651-4daa-a804-dd142f441358@linux.dev>
On 2025-11-14 10:31:45 [-0800], Yonghong Song wrote:
> > I believe that migration needs to be disabled at this point, but I am
> > again adding Yonghong on CC for his perspective.
>
> Yes, migration needs to be disabled for rt kernel in order to let
> bpf program running properly.
Why is disabling migration special in regard to RT kernels vs !RT?
Why do we need to disable migration given that bpf_prog_run_array()
already does that? Is there a different entry point?
My point why is it required to disable migration on trace-point entry
for BPF given that the BPF-entry already does so.
Sebastian
next prev parent reply other threads:[~2025-11-18 7:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 2:52 linux-next: manual merge of the rcu tree with the ftrace tree Stephen Rothwell
2025-11-14 12:42 ` Steven Rostedt
2025-11-14 13:35 ` Sebastian Andrzej Siewior
2025-11-14 15:46 ` Steven Rostedt
2025-11-14 16:00 ` Sebastian Andrzej Siewior
2025-11-14 16:22 ` Steven Rostedt
2025-11-14 16:33 ` Sebastian Andrzej Siewior
2025-11-14 16:48 ` Steven Rostedt
2025-11-14 17:02 ` Sebastian Andrzej Siewior
2025-11-14 17:11 ` Steven Rostedt
2025-11-14 17:00 ` Paul E. McKenney
2025-11-14 17:10 ` Sebastian Andrzej Siewior
2025-11-14 17:25 ` Paul E. McKenney
2025-11-14 17:40 ` Steven Rostedt
2025-11-14 17:41 ` Sebastian Andrzej Siewior
2025-11-14 18:26 ` Paul E. McKenney
2025-11-14 14:48 ` Frederic Weisbecker
2025-11-14 16:01 ` Steven Rostedt
2025-11-14 17:06 ` Paul E. McKenney
2025-11-14 18:58 ` Paul E. McKenney
2025-11-18 13:05 ` Frederic Weisbecker
2025-11-18 15:04 ` Paul E. McKenney
2025-12-02 0:57 ` Paul E. McKenney
2025-12-07 20:43 ` Paul E. McKenney
2025-12-08 0:17 ` Steven Rostedt
2025-12-08 4:21 ` Paul E. McKenney
2025-11-14 17:05 ` Paul E. McKenney
2025-11-14 18:31 ` Yonghong Song
2025-11-18 7:35 ` Sebastian Andrzej Siewior [this message]
2025-11-18 15:05 ` Paul E. McKenney
2025-11-30 18:49 ` Yonghong Song
2025-11-19 0:38 ` Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2025-11-06 1:24 Stephen Rothwell
2017-05-01 3:18 Stephen Rothwell
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=20251118073508.JdhVECQD@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=urezki@gmail.com \
--cc=yonghong.song@linux.dev \
/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