From: John Ogness <john.ogness@linutronix.de>
To: paulmck@kernel.org, rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
rostedt@goodmis.org, tglx@linutronix.de, pmladek@suse.com,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH v2 rcu 0/8] NMI-safe SRCU reader API
Date: Tue, 18 Oct 2022 12:39:40 +0206 [thread overview]
Message-ID: <87k04x4e0r.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20220929180714.GA2874192@paulmck-ThinkPad-P17-Gen-1>
Hi Paul,
On 2022-09-29, "Paul E. McKenney" <paulmck@kernel.org> wrote:
> This RFC series provides the second version of an NMI-safe SRCU reader
> API in the guise of srcu_read_lock_nmisafe() and
> srcu_read_unlock_nmisafe().
I would like to post a new series for printk that will rely on the
NMI-safe reader API. From the feedback of this series it appears that
the RFC v2 is an acceptable starting point. How should we proceed?
Will Frederic be sending a patch for the extra safety checks using
srcu_nmi_flags? Are you planning on posting a new version? Should I
include this or another version within my upcoming series?
Thanks for all your help on this!
John
next prev parent reply other threads:[~2022-10-18 10:34 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 14:46 [PATCH rcu 0/4] NMI-safe SRCU reader API Paul E. McKenney
2022-09-21 14:46 ` [PATCH RFC rcu 1/4] srcu: Convert ->srcu_lock_count and ->srcu_unlock_count to atomic Paul E. McKenney
2022-09-21 14:46 ` [PATCH RFC rcu 2/4] srcu: Create and srcu_read_lock_nmisafe() and srcu_read_unlock_nmisafe() Paul E. McKenney
2022-09-21 14:46 ` [PATCH RFC rcu 3/4] srcu: Check for consistent per-CPU per-srcu_struct NMI safety Paul E. McKenney
2022-09-21 14:46 ` [PATCH RFC rcu 4/4] srcu: Check for consistent global " Paul E. McKenney
2022-09-29 18:07 ` [PATCH v2 rcu 0/8] NMI-safe SRCU reader API Paul E. McKenney
2022-09-29 18:07 ` [PATCH RFC v2 rcu 1/8] srcu: Convert ->srcu_lock_count and ->srcu_unlock_count to atomic Paul E. McKenney
2022-09-30 15:02 ` John Ogness
2022-09-30 15:35 ` Paul E. McKenney
2022-09-30 20:37 ` John Ogness
2022-10-01 16:51 ` Paul E. McKenney
2022-09-29 18:07 ` [PATCH RFC v2 rcu 2/8] srcu: Create an srcu_read_lock_nmisafe() and srcu_read_unlock_nmisafe() Paul E. McKenney
2022-10-02 15:55 ` Frederic Weisbecker
2022-10-02 15:57 ` Frederic Weisbecker
2022-10-02 16:10 ` Paul E. McKenney
2022-10-02 16:09 ` Paul E. McKenney
2022-10-02 21:47 ` Frederic Weisbecker
2022-10-02 23:46 ` Paul E. McKenney
2022-10-03 9:55 ` Frederic Weisbecker
2022-10-03 11:52 ` Paul E. McKenney
2022-10-18 14:31 ` John Ogness
2022-10-18 15:18 ` Paul E. McKenney
2022-09-29 18:07 ` [PATCH RFC v2 rcu 3/8] srcu: Check for consistent per-CPU per-srcu_struct NMI safety Paul E. McKenney
2022-10-02 22:06 ` Frederic Weisbecker
2022-10-02 23:51 ` Paul E. McKenney
2022-10-03 10:13 ` Frederic Weisbecker
2022-10-03 11:57 ` Paul E. McKenney
2022-10-03 12:37 ` Frederic Weisbecker
2022-10-03 13:32 ` Paul E. McKenney
2022-10-03 13:36 ` Frederic Weisbecker
2022-09-29 18:07 ` [PATCH RFC v2 rcu 4/8] srcu: Check for consistent global " Paul E. McKenney
2022-09-29 18:07 ` [PATCH RFC v2 rcu 5/8] arch/x86: Add ARCH_HAS_NMI_SAFE_THIS_CPU_OPS Kconfig option Paul E. McKenney
2022-09-29 18:07 ` [PATCH RFC v2 rcu 6/8] arch/arm64: " Paul E. McKenney
2022-09-29 18:07 ` Paul E. McKenney
2022-10-05 11:12 ` Mark Rutland
2022-10-05 11:12 ` Mark Rutland
2022-09-29 18:07 ` [PATCH RFC v2 rcu 7/8] arch/loongarch: " Paul E. McKenney
2022-09-29 18:07 ` [PATCH RFC v2 rcu 8/8] arch/s390: " Paul E. McKenney
2022-10-03 14:11 ` [PATCH v2 rcu 0/8] NMI-safe SRCU reader API Frederic Weisbecker
2022-10-03 16:38 ` Paul E. McKenney
2022-10-14 22:47 ` Joel Fernandes
2022-10-14 22:52 ` Joel Fernandes
2022-10-18 10:33 ` John Ogness [this message]
2022-10-18 15:24 ` Paul E. McKenney
2022-10-18 18:44 ` John Ogness
2022-10-18 18:59 ` Paul E. McKenney
2022-10-18 21:57 ` Paul E. McKenney
2022-10-19 11:13 ` John Ogness
2022-10-19 19:14 ` Paul E. McKenney
2022-10-19 21:38 ` John Ogness
2022-10-19 22:05 ` Frederic Weisbecker
2022-10-20 22:27 ` Paul E. McKenney
2022-10-20 22:41 ` Paul E. McKenney
2022-10-21 12:27 ` John Ogness
2022-10-21 13:59 ` Paul E. McKenney
2022-10-21 18:41 ` Paul E. McKenney
2022-10-24 6:15 ` John Ogness
2022-10-24 13:47 ` Paul E. McKenney
2022-10-27 9:31 ` John Ogness
2022-10-27 14:10 ` Paul E. McKenney
2022-10-27 14:39 ` John Ogness
2022-10-27 16:01 ` 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=87k04x4e0r.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=frederic@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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 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.