From: Steven Rostedt <rostedt@goodmis.org>
To: Marco Elver <elver@google.com>
Cc: Petr Mladek <pmladek@suse.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
kasan-dev@googlegroups.com, Thomas Gleixner <tglx@linutronix.de>,
Johannes Berg <johannes.berg@intel.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Functional Testing <lkft@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: Make console tracepoint safe in NMI() context
Date: Fri, 15 Jul 2022 09:51:56 -0400 [thread overview]
Message-ID: <20220715095156.12a3a0e3@gandalf.local.home> (raw)
In-Reply-To: <CANpmjNOHY1GC_Fab4T6J06vqW0vRf=4jQR0dG0MJoFOPpKzcUA@mail.gmail.com>
On Fri, 15 Jul 2022 14:39:52 +0200
Marco Elver <elver@google.com> wrote:
> Couldn't this just use rcu_is_watching()?
>
> | * rcu_is_watching - see if RCU thinks that the current CPU is not idle
Maybe, but I was thinking that Petr had a way to hit the issue that we
worry about. But since the non _rcuide() call requires rcu watching,
prehaps that is better to use.
-- Steve
next prev parent reply other threads:[~2022-07-15 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 12:01 [PATCH] printk: Make console tracepoint safe in NMI() context Petr Mladek
2022-07-15 12:39 ` Marco Elver
2022-07-15 13:51 ` Steven Rostedt [this message]
2022-07-15 15:10 ` Paul E. McKenney
2022-07-15 15:25 ` Steven Rostedt
2022-07-15 15:34 ` Petr Mladek
2022-07-15 15:02 ` 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=20220715095156.12a3a0e3@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=johannes.berg@intel.com \
--cc=john.ogness@linutronix.de \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=senozhatsky@chromium.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.