From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: kan.liang@intel.com, jolsa@redhat.com, namhyung@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V7 1/1] perf tool:perf diff support for different binaries
Date: Thu, 26 Feb 2015 17:44:27 -0300 [thread overview]
Message-ID: <20150226204427.GE13373@kernel.org> (raw)
In-Reply-To: <20150226203404.GF27767@tassilo.jf.intel.com>
Em Thu, Feb 26, 2015 at 12:34:04PM -0800, Andi Kleen escreveu:
> > Having a nice explanation of the problem helps, as my first reaction to
> > this patch was: "What? This is what this tool is supposed to do, to
> > compare two versions of a binary, one that is being developed from the
> > same source, the other with slight modifications, etc", while the
> > description of the patch made it look as this was a feature that was now
> > being introduced.
>
> AFAIK it was actually to compare multiple runs of the same binary
> with different setups: e.g. varying number of threads.
>
> However in the Linux kernel development world it turns out comparing
> multiple similar binaries is much more useful.
Surely I am getting old and forgetting things, but when I wrote it, my
intent was to do:
vi a.c
build it
perf record a
vi a.c # change it
build it
perf record a
perf diff
And see if what I did while vi'ing it matched what I thought it would.
- Arnaldo
next prev parent reply other threads:[~2015-02-26 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 5:39 [PATCH V7 1/1] perf tool:perf diff support for different binaries kan.liang
2015-02-25 15:14 ` Liang, Kan
2015-02-25 15:30 ` acme
2015-02-26 15:17 ` Arnaldo Carvalho de Melo
2015-02-26 20:34 ` Andi Kleen
2015-02-26 20:44 ` Arnaldo Carvalho de Melo [this message]
2015-02-26 22:49 ` Andi Kleen
2015-02-28 9:32 ` [tip:perf/core] perf diff: Support " 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=20150226204427.GE13373@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--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 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.