From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Namhyung Kim <namhyung@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH] perf tools: Handle PERF_RECORD_HEADER_EVENT_TYPE properly
Date: Wed, 5 Feb 2014 11:24:50 -0200 [thread overview]
Message-ID: <20140205132450.GA3685@infradead.org> (raw)
In-Reply-To: <20140205090339.GB1201@krava.brq.redhat.com>
Em Wed, Feb 05, 2014 at 10:03:39AM +0100, Jiri Olsa escreveu:
> On Wed, Feb 05, 2014 at 06:55:52AM +0100, Ingo Molnar wrote:
> >
> > * Jiri Olsa <jolsa@redhat.com> wrote:
> >
> > > We removed event types from data file in following commits:
> > > 6065210 perf tools: Remove event types framework completely
> > > 44b3c57 perf tools: Remove event types from perf data file
> > >
> > > We no longer need this information, because we can get it
> > > directly from tracepoints.
> > >
> > > But we still need to handle PERF_RECORD_HEADER_EVENT_TYPE
> > > event for the sake of old perf data files created in pipe
> > > mode like:
> > >
> > > $ perf.3.4 record -o - foo >perf.data
> > > $ perf.312 report -i - < perf.data
> > >
> > > Reported-by: Stephane Eranian <eranian@google.com>
> > > Signed-off-by: Jiri Olsa <jolsa@redhat.com>
> > > Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>
> > > Cc: Frederic Weisbecker <fweisbec@gmail.com>
> > > Cc: Ingo Molnar <mingo@elte.hu>
> > > Cc: Namhyung Kim <namhyung@kernel.org>
> > > Cc: Paul Mackerras <paulus@samba.org>
> > > Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> > > Cc: David Ahern <dsahern@gmail.com>
> > > ---
> > > tools/perf/util/session.c | 6 ++++++
> > > 1 file changed, 6 insertions(+)
> > >
> > > diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
> > > index 0b39a48..5da6ce7 100644
> > > --- a/tools/perf/util/session.c
> > > +++ b/tools/perf/util/session.c
> > > @@ -1008,6 +1008,12 @@ static int perf_session__process_user_event(struct perf_session *session, union
> > > if (err == 0)
> > > perf_session__set_id_hdr_size(session);
> > > return err;
> > > + case PERF_RECORD_HEADER_EVENT_TYPE:
> > > + /*
> > > + * Depreceated, but we need to handle it for sake
> > > + * of old data files create in pipe mode.
> > > + */
> >
> > Two small speling nits:
> >
> > s/Depreceated
> > /Deprecated
> >
> > s/create
> > /created
> >
> > Ack otherwise.
> >
> > Thanks,
> >
> > Ingo
>
> ugh, my spell checker sux.. ;-\ acme, beer for each correction? ;-)
two for each, deal.
- Arnaldo
next prev parent reply other threads:[~2014-02-05 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 14:37 [PATCH] perf tools: Handle PERF_RECORD_HEADER_EVENT_TYPE properly Jiri Olsa
2014-02-05 5:55 ` Ingo Molnar
2014-02-05 9:03 ` Jiri Olsa
2014-02-05 13:24 ` Arnaldo Carvalho de Melo [this message]
2014-02-22 17:54 ` [tip:perf/core] " tip-bot for Jiri Olsa
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=20140205132450.GA3685@infradead.org \
--to=acme@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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