From: Milian Wolff <milian.wolff@kdab.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Andi Kleen <ak@linux.intel.com>,
acme@kernel.org, jolsa@kernel.org, Linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
David Ahern <dsahern@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Yao Jin <yao.jin@linux.intel.com>,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
kernel-team@lge.com
Subject: Re: [PATCH v6 1/6] perf report: properly handle branch count in match_chain
Date: Fri, 20 Oct 2017 12:21:35 +0200 [thread overview]
Message-ID: <4075632.NPQJP4Tzi9@agathebauer> (raw)
In-Reply-To: <20171019150108.GA24104@danjae.aot.lge.com>
On Donnerstag, 19. Oktober 2017 17:01:08 CEST Namhyung Kim wrote:
> Hi Andi,
>
> On Thu, Oct 19, 2017 at 06:55:19AM -0700, Andi Kleen wrote:
> > On Thu, Oct 19, 2017 at 12:59:14PM +0200, Milian Wolff wrote:
> > > On Donnerstag, 19. Oktober 2017 00:41:04 CEST Andi Kleen wrote:
> > > > Milian Wolff <milian.wolff@kdab.com> writes:
> > > > > +static enum match_result match_address_dso(struct dso *left_dso,
> > > > > u64
> > > > > left_ip, + struct dso *right_dso, u64 right_ip)
> > > > > +{
> > > > > + if (left_dso == right_dso && left_ip == right_ip)
> > > > > + return MATCH_EQ;
> > > > > + else if (left_ip < right_ip)
> > > > > + return MATCH_LT;
> > > > > + else
> > > > > + return MATCH_GT;
> > > > > +}
> > > >
> > > > So why does only the first case check the dso? Does it not matter
> > > > for the others?
> > > >
> > > > Either should be checked by none or by all.
> > >
> > > I don't see why it should be checked. It is only required to prevent two
> > > addresses to be considered equal while they are not. So only the one
> > > check is required, otherwise we return either LT or GT.
> >
> > When the comparison is always in the same process (which I think
> > is not the case) just checking the addresses is sufficient. If they are
> > not then you always need to check the DSO and only compare inside the
> > same DSO.
>
> As far as I know, the node->ip is a relative address (inside a DSO).
> So it should compare the dso as well even in the same process.
Sorry guys, I seem to be slow at understanding your review comments.
match_address_dso should impose a sort order on two relative addresses. The
order should ensure that relative addresses in a different DSO are not
considered equal. But if the DSOs are different, it doesn't matter whether we
return LT or GT - or?
Put differently, how would you write this function to take care of the DSO in
the other two branches? I.e. what to return if the DSOs are different - a
MATCH_ERROR?
Bye
--
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
next prev parent reply other threads:[~2017-10-20 10:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 18:53 [PATCH v6 0/6] generate full callchain cursor entries for inlined frames Milian Wolff
2017-10-18 18:53 ` [PATCH v6 1/6] perf report: properly handle branch count in match_chain Milian Wolff
2017-10-18 22:41 ` Andi Kleen
2017-10-19 10:59 ` Milian Wolff
2017-10-19 13:55 ` Andi Kleen
2017-10-19 15:01 ` Namhyung Kim
2017-10-20 10:21 ` Milian Wolff [this message]
2017-10-20 11:38 ` Milian Wolff
2017-10-20 13:39 ` Arnaldo Carvalho de Melo
2017-10-23 5:19 ` Namhyung Kim
2017-10-20 15:22 ` Arnaldo Carvalho de Melo
2017-10-20 19:52 ` Milian Wolff
2017-10-18 18:53 ` [PATCH v6 2/6] perf report: cache failed lookups of inlined frames Milian Wolff
2017-10-18 18:53 ` [PATCH v6 3/6] perf report: cache srclines for callchain nodes Milian Wolff
2017-10-18 18:53 ` [PATCH v6 4/6] perf report: use srcline from callchain for hist entries Milian Wolff
2017-10-18 18:53 ` [PATCH v6 5/6] perf util: enable handling of inlined frames by default Milian Wolff
2017-10-18 18:53 ` [PATCH v6 6/6] perf util: use correct IP mapping to find srcline for hist entry Milian Wolff
2017-10-19 10:54 ` Milian Wolff
2017-10-20 5:15 ` Namhyung Kim
2017-10-24 8:51 ` Milian Wolff
2017-10-25 1:46 ` Namhyung Kim
2017-10-30 20:03 ` Arnaldo Carvalho de Melo
2017-10-30 23:35 ` Namhyung Kim
2017-10-18 22:43 ` [PATCH v6 0/6] generate full callchain cursor entries for inlined frames Andi Kleen
2017-10-20 15:43 ` Arnaldo Carvalho de Melo
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=4075632.NPQJP4Tzi9@agathebauer \
--to=milian.wolff@kdab.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@lge.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=yao.jin@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).