From: Robert Richter <robert.richter@amd.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "acme@redhat.com" <acme@ghostprotocols.net>,
Stephane Eranian <eranian@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"dsahern@gmail.com" <dsahern@gmail.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"mingo@elte.hu" <mingo@elte.hu>
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v8)
Date: Thu, 1 Dec 2011 16:15:20 +0100 [thread overview]
Message-ID: <20111201151520.GB15738@erda.amd.com> (raw)
In-Reply-To: <20111201150151.GA15110@somewhere.redhat.com>
On 01.12.11 16:01:55, Frederic Weisbecker wrote:
> On Wed, Nov 30, 2011 at 02:49:46PM -0200, acme@redhat.com wrote:
> > Em Wed, Nov 30, 2011 at 04:08:29PM +0100, Robert Richter escreveu:
> > > On 29.11.11 10:35:24, Stephane Eranian wrote:
> > > > sec_start = header->data_offset + header->data_size;
> > > > lseek(fd, sec_start + sec_size, SEEK_SET);
> > > >
> > > > err = do_write_feat(fd, header, HEADER_TRACE_INFO, &p, evlist);
> > > > if (err)
> > > > goto out_free;
> > > >
> > > > err = do_write_feat(fd, header, HEADER_BUILD_ID, &p, evlist);
> > > > if (err) {
> > > > perf_header__clear_feat(header, HEADER_BUILD_ID);
> > > > goto out_free;
> > > > }
> >
> > > > The 'clear_feat' is missing for TRACE_INFO, that's all. The question is:
> > > > is case do_write_feat(trace_info) fails, is there still a way to parse the file
> > > > correctly? If not, then perf should bail out, if yes, then we need to add the
> > > > clear_feat(TRACE_INFO) in case of error.
> >
> > > The question is, if do_write_feat() fails for HEADER_TRACE_INFO or
> > > HEADER_BUILD_ID then perf_header__adds_write() fails. A failure of any
> > > other feature simple disables it by calling clear_feat(). I noticed
> > > this asymmetry and wonder why?
>
> Not sure either. I must confess I didn't write that fixup part...
I am asking this because I want to change code in a way that treats
all features the same, that is just to disable the feature bit on
failure and then continue anyway.
>
> > >
> > > Also, is there a reason why HEADER_TRACE_INFO starts with bit 1 instead
> > > of bit 0. Is bit 0 reserved for some reason?
>
> Looks like a mistake I made from the beginning. And we can't really fix that
> without breaking all perf.data :)
Ok, wasn't sure if the bit was used for other purposes, but seems to
be always zero then.
Thanks,
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
next prev parent reply other threads:[~2011-12-01 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 13:40 [PATCH] perf: make perf.data more self-descriptive (v8) Stephane Eranian
2011-10-04 4:50 ` David Ahern
2011-11-29 18:22 ` Robert Richter
2011-11-29 18:35 ` Stephane Eranian
2011-11-30 15:08 ` Robert Richter
2011-11-30 16:49 ` acme
2011-12-01 15:01 ` Frederic Weisbecker
2011-12-01 15:15 ` Robert Richter [this message]
2011-12-01 17:53 ` Stephane Eranian
2011-12-05 13:23 ` Robert Richter
2011-12-05 19:24 ` Stephane Eranian
2011-12-06 9:29 ` Robert Richter
[not found] ` <CABPqkBRbdJ0tG2+V-CvEdPnwm5YqQuv7FKrUHoTM8=wa8V=kHQ@mail.gmail.com>
2011-12-19 9:26 ` Robert Richter
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=20111201151520.GB15738@erda.amd.com \
--to=robert.richter@amd.com \
--cc=acme@ghostprotocols.net \
--cc=ak@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.