From: Jiri Olsa <jolsa@redhat.com>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
"acme@kernel.org" <acme@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ak@linux.intel.com" <ak@linux.intel.com>
Subject: Re: [PATCH V5 3/3] perf tool: check buildid for symoff
Date: Fri, 28 Nov 2014 10:49:26 +0100 [thread overview]
Message-ID: <20141128094926.GB27703@krava.brq.redhat.com> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F07701676CB2@SHSMSX103.ccr.corp.intel.com>
On Thu, Nov 27, 2014 at 02:09:51PM +0000, Liang, Kan wrote:
>
>
> > Hi Kan,
> >
> > On Mon, 24 Nov 2014 11:00:29 -0500, Kan Liang wrote:
> > > From: Kan Liang <kan.liang@intel.com>
> > >
> > > symoff can support both same binaries and different binaries. However,
> > > the offset may be changed for different binaries. This patch checks
> > > the buildid of perf.data. If they are from different binaries, print a
> > > warning to notify the user.
> >
> > Hmm.. I think that perf diff is supposed to compare performance between
> > different (i.e. modified) binaries. So there's a little point to print the
> > warning IMHO - but I'm not insist it strongly..
> >
> > Anyway, I think what we really need for the warning is different version of
> > same binary. For example, if data file 1 has DSO A and B, and data file 2 has
> > DSO B and C, we should not consider they're different (unless build-ids of B
> > in data file 1 and 2 are different) since A and C won't affect symoff
> > comparision.
that sounds good to me
> >
>
> It looks good.
> But I still slightly prefer to warn/inform the user if there are any different dsos,
> not just from common part. But it's not a strong option.
> I'd like to hear from others.
>
> Arnaldo? Jirka?
sorry for late reply.. anyway like I said in the other email
---
IMO one (WARN_ONCE style) warning by default if we see
buildids discrepancy and detailed comparison for --verbose
---
I think the breakage of the check (that Namhyung described) could
be mentioned/labeled somehow as serious issue in the warning and
we could also 'inform' about "any different dsos" as you mentioned
jirka
>
> Thanks,
> Kan
>
> > Thanks,
> > Namhyung
next prev parent reply other threads:[~2014-11-28 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 16:00 [PATCH V5 1/3] perf tool: Add sort key symoff for perf diff Kan Liang
2014-11-24 16:00 ` [PATCH V5 2/3] perf tool: new function to compare build_ids Kan Liang
2014-11-24 16:00 ` [PATCH V5 3/3] perf tool: check buildid for symoff Kan Liang
2014-11-25 11:51 ` Jiri Olsa
2014-11-26 16:10 ` Liang, Kan
2014-11-28 9:43 ` Jiri Olsa
2014-11-25 12:21 ` Jiri Olsa
2014-11-25 17:19 ` Liang, Kan
2014-11-27 2:05 ` Namhyung Kim
2014-11-27 14:09 ` Liang, Kan
2014-11-28 9:49 ` Jiri Olsa [this message]
2014-11-28 16:43 ` Liang, Kan
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=20141128094926.GB27703@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.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®