From: Frederic Weisbecker <frederic@kernel.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
Neeraj Upadhyay <Neeraj.Upadhyay@amd.com>
Subject: Re: [PATCH v2 0/6] RCU tasks fixes for v6.9
Date: Thu, 22 Feb 2024 17:52:23 +0100 [thread overview]
Message-ID: <Zdd7x4Rmy_-WDqfl@localhost.localdomain> (raw)
In-Reply-To: <20240217012745.3446231-1-boqun.feng@gmail.com>
Le Fri, Feb 16, 2024 at 05:27:35PM -0800, Boqun Feng a écrit :
> Hi,
>
> This series contains the fixes of RCU tasks for v6.9. You can also find
> the series at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git rcu-tasks.2024.02.14a
>
> Changes since v1:
>
> * Update with Paul's rework on "Eliminate deadlocks involving
> do_exit() and RCU task"
>
> The detailed list of changes:
>
> Paul E. McKenney (6):
> rcu-tasks: Repair RCU Tasks Trace quiescence check
> rcu-tasks: Add data to eliminate RCU-tasks/do_exit() deadlocks
> rcu-tasks: Initialize data to eliminate RCU-tasks/do_exit() deadlocks
> rcu-tasks: Maintain lists to eliminate RCU-tasks/do_exit() deadlocks
> rcu-tasks: Eliminate deadlocks involving do_exit() and RCU tasks
Food for later thoughts and further improvements: would it make sense to
call exit_rcu_tasks_start() on fork() instead and rely solely on
each CPUs' rtp_exit_list instead of the tasklist?
Thanks.
> rcu-tasks: Maintain real-time response in rcu_tasks_postscan()
>
> include/linux/rcupdate.h | 4 +-
> include/linux/sched.h | 2 +
> init/init_task.c | 1 +
> kernel/fork.c | 1 +
> kernel/rcu/tasks.h | 110 ++++++++++++++++++++++++++++++---------
> 5 files changed, 90 insertions(+), 28 deletions(-)
>
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-02-22 16:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 1:27 [PATCH v2 0/6] RCU tasks fixes for v6.9 Boqun Feng
2024-02-17 1:27 ` [PATCH v2 1/6] rcu-tasks: Repair RCU Tasks Trace quiescence check Boqun Feng
2024-02-17 1:27 ` [PATCH v2 2/6] rcu-tasks: Add data to eliminate RCU-tasks/do_exit() deadlocks Boqun Feng
2024-02-22 16:54 ` Frederic Weisbecker
2024-02-22 20:46 ` Paul E. McKenney
2024-02-17 1:27 ` [PATCH v2 3/6] rcu-tasks: Initialize " Boqun Feng
2024-02-22 16:21 ` Frederic Weisbecker
2024-02-22 20:41 ` Paul E. McKenney
2024-02-23 11:39 ` Frederic Weisbecker
2024-02-17 1:27 ` [PATCH v2 4/6] rcu-tasks: Maintain lists " Boqun Feng
2024-02-22 16:32 ` Frederic Weisbecker
2024-02-23 12:19 ` Frederic Weisbecker
2024-02-24 0:28 ` Paul E. McKenney
2024-02-17 1:27 ` [PATCH v2 5/6] rcu-tasks: Eliminate deadlocks involving do_exit() and RCU tasks Boqun Feng
2024-02-22 16:46 ` Frederic Weisbecker
2024-02-17 1:27 ` [PATCH v2 6/6] rcu-tasks: Maintain real-time response in rcu_tasks_postscan() Boqun Feng
2024-02-22 17:48 ` Frederic Weisbecker
2024-02-22 20:52 ` Paul E. McKenney
2024-02-22 22:56 ` Paul E. McKenney
2024-02-23 12:17 ` Frederic Weisbecker
2024-02-23 15:14 ` Frederic Weisbecker
2024-02-24 0:23 ` Paul E. McKenney
2024-02-22 16:52 ` Frederic Weisbecker [this message]
2024-02-22 22:09 ` [PATCH v2 0/6] RCU tasks fixes for v6.9 Paul E. McKenney
2024-02-23 12:25 ` Frederic Weisbecker
2024-02-24 0:43 ` Paul E. McKenney
2024-02-26 13:56 ` Frederic Weisbecker
2024-02-26 14:37 ` 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=Zdd7x4Rmy_-WDqfl@localhost.localdomain \
--to=frederic@kernel.org \
--cc=Neeraj.Upadhyay@amd.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rcu@vger.kernel.org \
/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