From: Petr Mladek <pmladek@suse.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Marco Elver <elver@google.com>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
linux-kernel@vger.kernel.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>,
Linux Kernel Functional Testing <lkft@linaro.org>
Subject: Re: [PATCH -printk] printk, tracing: fix console tracepoint
Date: Fri, 15 Jul 2022 11:40:16 +0200 [thread overview]
Message-ID: <20220715094016.GD24338@pathway.suse.cz> (raw)
In-Reply-To: <20220714111749.0a802e7f@gandalf.local.home>
On Thu 2022-07-14 11:17:49, Steven Rostedt wrote:
> Although printk is not really a fast path, you could do this and avoid the
> check when the trace event is not active:
>
> (Not even compiled tested)
>
> Tweaked the comment, and used raw_smp_processor_id() as I'm not sure we are
> in a preempt disabled context, and we don't care if we are not.
Makes sense.
> diff --git a/include/trace/events/printk.h b/include/trace/events/printk.h
> index 13d405b2fd8b..d0a5f63920bb 100644
> --- a/include/trace/events/printk.h
> +++ b/include/trace/events/printk.h
> @@ -7,11 +7,20 @@
>
> #include <linux/tracepoint.h>
>
> -TRACE_EVENT(console,
> +TRACE_EVENT_CONDITION(console,
> TP_PROTO(const char *text, size_t len),
>
> TP_ARGS(text, len),
>
> + /*
> + * trace_console_rcuidle() is not working in NMI. printk()
> + * is used more often in NMI than in rcuidle context.
> + * Choose the less evil solution here.
> + *
> + * raw_smp_processor_id() is reliable in rcuidle context.
> + */
> + TP_CONDITION(!rcu_is_idle_cpu(raw_smp_processor_id())),
> +
> TP_STRUCT__entry(
> __dynamic_array(char, msg, len + 1)
> ),
It looks better. I am going to test it and send as a proper patch
for review.
Thanks for help.
Best Regards,
Petr
next prev parent reply other threads:[~2022-07-15 9:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 7:38 [PATCH -printk] printk, tracing: fix console tracepoint Marco Elver
2022-05-03 16:15 ` Steven Rostedt
2022-05-03 19:14 ` John Ogness
2022-05-04 9:46 ` Petr Mladek
2022-05-06 14:51 ` Petr Mladek
2022-05-06 14:55 ` Marco Elver
2022-07-11 22:29 ` Steven Rostedt
2022-07-12 0:21 ` Paul E. McKenney
2022-07-12 0:53 ` Steven Rostedt
2022-07-12 2:57 ` Paul E. McKenney
2022-07-12 11:49 ` Paul E. McKenney
2022-07-12 13:39 ` Steven Rostedt
2022-07-12 13:49 ` Paul E. McKenney
2022-07-12 14:53 ` Steven Rostedt
2022-07-12 15:16 ` Paul E. McKenney
2022-07-13 11:25 ` Petr Mladek
2022-07-13 14:05 ` Paul E. McKenney
2022-07-14 14:53 ` Petr Mladek
2022-07-14 15:17 ` Steven Rostedt
2022-07-15 9:40 ` Petr Mladek [this message]
2022-07-12 15:25 ` Petr Mladek
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=20220715094016.GD24338@pathway.suse.cz \
--to=pmladek@suse.com \
--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=rostedt@goodmis.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox