From: Steven Rostedt <rostedt@goodmis.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH] tools lib traceevent: Split pevent_print_event() into specific functionality functions
Date: Thu, 25 Feb 2016 15:17:33 -0500 [thread overview]
Message-ID: <20160225151733.285b9223@gandalf.local.home> (raw)
In-Reply-To: <20160225201413.GS8720@kernel.org>
On Thu, 25 Feb 2016 17:14:13 -0300
Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> Em Thu, Feb 25, 2016 at 12:20:33PM -0500, Steven Rostedt escreveu:
> > Currently there's a single function that is used to display a record's
> > data in human readable format. That's pevent_print_event().
> > Unfortunately, this gives little room for adding other output within
> > the line without updating that function call.
> >
> > I've decided to split that function into 3 parts.
> >
> > pevent_print_event_task() which prints the task comm, pid and the CPU
> > pevent_print_event_time() which outputs the record's timestamp
> > pevent_print_event_data() which outputs the rest of the event data.
> >
> > pevent_print_event() now simply calls these three functions.
> >
> > To save time from doing the search for event from the record's type, I
> > created a new helper function called pevent_find_event_by_record(),
> > which returns the record's event, and this event has to be passed to
> > the above functions.
> >
> > Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> > ---
> > diff --git a/event-parse.c b/event-parse.c
> > index 18e93e430b8b..559d77381a60 100644
> > --- a/event-parse.c
> > +++ b/event-parse.c
>
>
> Isn't this on tools/lib/traceevent?
>
Oops, I did the change from trace-cmd. I'll repost.
Sorry ;-)
-- Steve
prev parent reply other threads:[~2016-02-25 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 17:20 Steven Rostedt
2016-02-25 20:14 ` Arnaldo Carvalho de Melo
2016-02-25 20:17 ` Steven Rostedt [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=20160225151733.285b9223@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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
all inboxes | Powered by JetHome®