From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "jbaron@akamai.com" <jbaron@akamai.com>,
"mingo@redhat.com" <mingo@redhat.com>, kernel <kernel@axis.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"pmladek@suse.com" <pmladek@suse.com>,
"sergey.senozhatsky@gmail.com" <sergey.senozhatsky@gmail.com>,
"john.ogness@linutronix.de" <john.ogness@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dynamic debug: allow printing to trace event
Date: Tue, 25 Aug 2020 17:39:50 +0200 [thread overview]
Message-ID: <20200825153950.zza53vsl6wsehgh2@axis.com> (raw)
In-Reply-To: <20200814131531.01b43c91@oasis.local.home>
On Fri, Aug 14, 2020 at 07:15:31PM +0200, Steven Rostedt wrote:
> On Fri, 14 Aug 2020 15:31:51 +0200
> Vincent Whitchurch <vincent.whitchurch@axis.com> wrote:
> > index aa9ff9e1c0b3..f599ed21ecc5 100644
> > --- a/include/linux/dynamic_debug.h
> > +++ b/include/linux/dynamic_debug.h
> > @@ -27,13 +27,16 @@ struct _ddebug {
> > * writes commands to <debugfs>/dynamic_debug/control
> > */
> > #define _DPRINTK_FLAGS_NONE 0
> > -#define _DPRINTK_FLAGS_PRINT (1<<0) /* printk() a message using the format */
> > +#define _DPRINTK_FLAGS_PRINTK (1<<0) /* printk() a message using the format */
>
> The above looks like a cleanup unrelated to this patch, and probably
> should be on its own.
I've moved this and the other renaming hunk out to a separate patch.
> > #define _DPRINTK_FLAGS_INCL_MODNAME (1<<1)
> > #define _DPRINTK_FLAGS_INCL_FUNCNAME (1<<2)
> > #define _DPRINTK_FLAGS_INCL_LINENO (1<<3)
> > #define _DPRINTK_FLAGS_INCL_TID (1<<4)
> > +#define _DPRINTK_FLAGS_TRACE (1<<5)
> > +#define _DPRINTK_FLAGS_PRINT (_DPRINTK_FLAGS_PRINTK | \
> > + _DPRINTK_FLAGS_TRACE)
> > #if defined DEBUG
> > -#define _DPRINTK_FLAGS_DEFAULT _DPRINTK_FLAGS_PRINT
> > +#define _DPRINTK_FLAGS_DEFAULT _DPRINTK_FLAGS_PRINTK
> > #else
> > #define _DPRINTK_FLAGS_DEFAULT 0
> > #endif
> > diff --git a/include/trace/events/printk.h b/include/trace/events/printk.h
> > index 13d405b2fd8b..6c89121a1669 100644
> > --- a/include/trace/events/printk.h
> > +++ b/include/trace/events/printk.h
> > @@ -7,7 +7,7 @@
> >
> > #include <linux/tracepoint.h>
> >
> > -TRACE_EVENT(console,
> > +DECLARE_EVENT_CLASS(printk,
> > TP_PROTO(const char *text, size_t len),
> >
> > TP_ARGS(text, len),
> > @@ -31,6 +31,16 @@ TRACE_EVENT(console,
> >
> > TP_printk("%s", __get_str(msg))
> > );
> > +
> > +DEFINE_EVENT(printk, console,
> > + TP_PROTO(const char *text, size_t len),
> > + TP_ARGS(text, len)
> > +);
> > +
> > +DEFINE_EVENT(printk, dynamic,
>
> Can we call this "dynamic_printk" or "printk_dynamic", as
> trace_dynamic() is too generic.
I went for "dyndbg" (printk:dyndbg / trace_dyndbg()) which is the
documented name of the infrastructure.
prev parent reply other threads:[~2020-08-25 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 13:31 Vincent Whitchurch
2020-08-14 17:15 ` Steven Rostedt
2020-08-14 21:30 ` Jason Baron
2020-08-25 15:32 ` Vincent Whitchurch
2020-08-25 15:39 ` Vincent Whitchurch [this message]
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=20200825153950.zza53vsl6wsehgh2@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=corbet@lwn.net \
--cc=jbaron@akamai.com \
--cc=john.ogness@linutronix.de \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
/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
all inboxes | Powered by JetHome®