From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] perf tools: Provide backward compatibility with previous perf.data version
Date: Thu, 8 Oct 2009 22:28:30 +0200 [thread overview]
Message-ID: <20091008202828.GF5073@nowhere> (raw)
In-Reply-To: <20091008201222.GB30594@elte.hu>
On Thu, Oct 08, 2009 at 10:12:22PM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > We have merged the trace.info file into perf.data by adding one
> > section in the perf headers. This makes it incompatible with previous
> > version: the new perf tools can't read the older perf.data.
> >
> > To support the previous format, we check the headers size. If they
> > have the same size than in the previous format, then ignore the trace
> > info section that doesn't exist.
> >
> > Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> > Cc: Mike Galbraith <efault@gmx.de>
> > Cc: Paul Mackerras <paulus@samba.org>
> > ---
> > tools/perf/util/header.c | 8 +++++++-
> > 1 files changed, 7 insertions(+), 1 deletions(-)
> >
> > diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> > index 212fade..9aae360 100644
> > --- a/tools/perf/util/header.c
> > +++ b/tools/perf/util/header.c
> > @@ -287,10 +287,16 @@ struct perf_header *perf_header__read(int fd)
> > do_read(fd, &f_header, sizeof(f_header));
> >
> > if (f_header.magic != PERF_MAGIC ||
> > - f_header.size != sizeof(f_header) ||
> > f_header.attr_size != sizeof(f_attr))
> > die("incompatible file format");
> >
> > + if (f_header.size != sizeof(f_header)) {
> > + /* Support the previous format */
> > + if (f_header.size == offsetof(typeof(f_header), trace_info))
> > + f_header.trace_info.size = 0;
> > + else
> > + die("incompatible file format");
> > + }
> > nr_attrs = f_header.attrs.size / sizeof(f_attr);
> > lseek(fd, f_header.attrs.offset, SEEK_SET);
>
> Perfect - thanks Frederic!
>
> This should handle most of the (non-trace) perf.data's out there.
Yeah, hopefully. I've only tested in a simple old perf.data but
that should do the trick for all of the non-trace files.
> trace.info is not something we really want to be backwards compatible
> about, if we can avoid it.
>
> Ingo
Yeah, that said, it's still possible and wouldn't require too much changes.
May be let's wait for complaints and, if any, I can provide this backward
support too.
Thanks.
next prev parent reply other threads:[~2009-10-08 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 20:07 [PATCH] perf tools: Provide backward compatibility with previous perf.data version Frederic Weisbecker
2009-10-08 20:12 ` Ingo Molnar
2009-10-08 20:28 ` Frederic Weisbecker [this message]
2009-10-08 20:31 ` Ingo Molnar
2009-10-08 20:16 ` [tip:perf/core] " tip-bot for Frederic Weisbecker
2009-10-08 20:22 ` [PATCH] " Frederic Weisbecker
2009-10-12 9:10 ` Ingo Molnar
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=20091008202828.GF5073@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.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