From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Karol Herbst <karolherbst@gmail.com>,
Pekka Paalanen <ppaalanen@gmail.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org
Subject: Re: [PATCH 2/2] x86/mm/kmmio: Remove rcu_read_lock()
Date: Fri, 9 Dec 2022 13:03:34 -0500 [thread overview]
Message-ID: <20221209130334.487b63aa@gandalf.local.home> (raw)
In-Reply-To: <20221207173621.GF4001@paulmck-ThinkPad-P17-Gen-1>
On Wed, 7 Dec 2022 09:36:21 -0800
"Paul E. McKenney" <paulmck@kernel.org> wrote:
> > Cc: "Paul E. McKenney" <paulmck@kernel.org>
> > Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
>
> Might be worth adding a comment saying that others are using this
> preempt_disable() to block an RCU grace period, but that is up to
> you guys. I will let you and your future selves be the judges.
Good point. I'll add a comment in v2.
>
> Acked-by: Paul E. McKenney <paulmck@kernel.org>
Thanks!
-- Steve
next prev parent reply other threads:[~2022-12-09 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 19:12 [PATCH 0/2] x86/mm/kmmio: Have mmiotracer play nice with lockdep Steven Rostedt
2022-12-06 19:12 ` [PATCH 1/2] x86/mm/kmmio: Switch to arch_spin_lock() Steven Rostedt
2022-12-06 19:12 ` [PATCH 2/2] x86/mm/kmmio: Remove rcu_read_lock() Steven Rostedt
2022-12-07 17:36 ` Paul E. McKenney
2022-12-09 18:03 ` Steven Rostedt [this message]
2022-12-09 18:09 ` Steven Rostedt
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=20221209130334.487b63aa@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=karolherbst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=ppaalanen@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).