public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "acme@kernel.org" <acme@kernel.org>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dima@secretsauce.net" <dima@secretsauce.net>,
	"jolsa@redhat.com" <jolsa@redhat.com>,
	"namhyung@kernel.org" <namhyung@kernel.org>,
	"andi@firstfloor.org" <andi@firstfloor.org>
Subject: Re: [PATCH] perf diff: bug fix, donot overwrite valid build id
Date: Mon, 19 Dec 2016 15:37:58 -0300	[thread overview]
Message-ID: <20161219183758.GC551@kernel.org> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F07753682E46@SHSMSX103.ccr.corp.intel.com>

Em Mon, Dec 19, 2016 at 02:53:30PM +0000, Liang, Kan escreveu:
> Hi Arnaldo,
> 
> Ping
> 
> Are you OK with the fix?

Yeah, looks ok, will merge it.

- Arnaldo
 
> Thanks,
> Kan
> 
> > 
> > From: Kan Liang <kan.liang@intel.com>
> > 
> > Fixes a perf diff regression issue which was introduced by commit
> > 5baecbcd9c9a ("perf symbols: we can now read separate debug-info files
> > based on a build ID")
> > 
> > The binary name could be same when perf diff different binaries. Build id is
> > used to distinguish between them.
> > However, the previous patch assumes the same binary name has same
> > build id. So it overwrites the build id according to the binary name,
> > regardless of whether the build id is set or not.
> > 
> > Check the has_build_id in dso__load. If the build id is already set, use it.
> > 
> > Before the fix applies,
> >  sudo ./perf diff 1.perf.data 2.perf.data  # Event 'cycles'
> >  #
> >  # Baseline    Delta  Shared Object     Symbol
> >  # ........  .......  ................  .............................
> >  #
> >     99.83%  -99.80%  tchain_edit       [.] f2
> >      0.12%  +99.81%  tchain_edit       [.] f3
> >      0.02%   -0.01%  [ixgbe]           [k] ixgbe_read_reg
> > 
> > After the fix applies,
> >  sudo ./perf diff 1.perf.data 2.perf.data  # Event 'cycles'
> >  #
> >  # Baseline    Delta  Shared Object     Symbol
> >  # ........  .......  ................  .............................
> >  #
> >     99.83%   +0.10%  tchain_edit       [.] f3
> >      0.12%   -0.08%  tchain_edit       [.] f2
> > 
> > Signed-off-by: Kan Liang <kan.liang@intel.com>
> > ---
> >  tools/perf/util/symbol.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c index
> > df2482b..dc93940 100644
> > --- a/tools/perf/util/symbol.c
> > +++ b/tools/perf/util/symbol.c
> > @@ -1459,7 +1459,8 @@ int dso__load(struct dso *dso, struct map *map)
> >  	 * Read the build id if possible. This is required for
> >  	 * DSO_BINARY_TYPE__BUILDID_DEBUGINFO to work
> >  	 */
> > -	if (is_regular_file(dso->long_name) &&
> > +	if (!dso->has_build_id &&
> > +	    is_regular_file(dso->long_name) &&
> >  	    filename__read_build_id(dso->long_name, build_id,
> > BUILD_ID_SIZE) > 0)
> >  		dso__set_build_id(dso, build_id);
> > 
> > --
> > 2.4.3

  reply	other threads:[~2016-12-19 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 15:29 [PATCH] perf diff: bug fix, donot overwrite valid build id kan.liang
2016-12-19 14:53 ` Liang, Kan
2016-12-19 18:37   ` acme [this message]
2016-12-20 19:30 ` [tip:perf/urgent] perf diff: Do not " tip-bot for Kan Liang

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=20161219183758.GC551@kernel.org \
    --to=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=dima@secretsauce.net \
    --cc=jolsa@redhat.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