From: Steven Rostedt <rostedt@goodmis.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Julia Cartwright <julia@ni.com>,
Daniel Wagner <daniel.wagner@siemens.com>,
tom.zanussi@linux.intel.com
Subject: Re: [PATCH RT 3/5] tracing: Restore proper field flag printing when displaying triggers
Date: Wed, 16 May 2018 11:45:35 -0400 [thread overview]
Message-ID: <20180516114535.6c3dbd1b@gandalf.local.home> (raw)
In-Reply-To: <20180516153213.mh5zgxzd2hwnkvuh@linutronix.de>
On Wed, 16 May 2018 17:32:14 +0200
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> On 2018-05-16 09:36:45 [-0400], Steven Rostedt wrote:
> > diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
> > index 9dac8bae4f34..4745ed588607 100644
> > --- a/kernel/trace/trace_events_hist.c
> > +++ b/kernel/trace/trace_events_hist.c
> > @@ -4916,6 +4916,16 @@ static void hist_field_print(struct seq_file *m, struct hist_field *hist_field)
> > seq_printf(m, "%s", field_name);
> > } else if (hist_field->flags & HIST_FIELD_FL_TIMESTAMP)
> > seq_puts(m, "common_timestamp");
> > +
> > + if (hist_field->flags) {
> > + if (!(hist_field->flags & HIST_FIELD_FL_VAR_REF) &&
> > + !(hist_field->flags & HIST_FIELD_FL_EXPR)) {
> > + const char *flags = get_hist_field_flags(hist_field);
> > +
> > + if (flags)
> > + seq_printf(m, ".%s", flags);
> > + }
> > + }
> > }
> >
> > static int event_hist_trigger_print(struct seq_file *m,
>
> For v4.16 I needed commit 0ae7961e75c3 ("tracing: Fix display of hist
> trigger expressions containing timestamps") in order to get this one
Yes, I assumed you had it as you pulled it into 4.14-rt. I was just
looking at what 4.14-rt has. Anything you added there you should add to
4.16-rt as well.
> cleanly applied. Comparing with -rc3 it looks like commit 5e4cf2bf6d1c
> ("tracing: Fix a potential NULL dereference") would be great addition.
Good catch, yeah, I should pull that in too.
>
> Safe to take them, right?
Yep.
-- Steve
next prev parent reply other threads:[~2018-05-16 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 13:36 [PATCH RT 0/5] Linux 4.14.40-rt31-rc1 Steven Rostedt
2018-05-16 13:36 ` [PATCH RT 1/5] tracing: Add field modifier parsing hist error for hist triggers Steven Rostedt
2018-05-16 13:36 ` [PATCH RT 2/5] tracing: Add field " Steven Rostedt
2018-05-16 13:36 ` [PATCH RT 3/5] tracing: Restore proper field flag printing when displaying triggers Steven Rostedt
2018-05-16 15:32 ` Sebastian Andrzej Siewior
2018-05-16 15:45 ` Steven Rostedt [this message]
2018-05-16 13:36 ` [PATCH RT 4/5] tracing: Uninitialized variable in create_tracing_map_fields() Steven Rostedt
2018-05-16 13:36 ` [PATCH RT 5/5] Linux 4.14.40-rt31-rc1 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=20180516114535.6c3dbd1b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@siemens.com \
--cc=jkacur@redhat.com \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.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;
as well as URLs for NNTP newsgroup(s).