From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Anton Blanchard <anton@samba.org>
Cc: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
chris.ryder@arm.com, peterz@infradead.org,
linux-kernel@vger.kernel.org, npiggin@gmail.com,
alexander.shishkin@linux.intel.com, mingo@redhat.com,
paulus@samba.org, mhiramat@kernel.org,
linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>,
Madhavan Srinivasan <masriniv@in.ibm.com>
Subject: Re: [PATCH] perf TUI: Don't throw error for zero length symbols
Date: Mon, 19 Dec 2016 15:15:17 -0300 [thread overview]
Message-ID: <20161219181517.GA551@kernel.org> (raw)
In-Reply-To: <20161217072754.32e6f492@kryten>
Em Sat, Dec 17, 2016 at 07:27:54AM +1100, Anton Blanchard escreveu:
> Hi Ravi,
>
> > > perf report (with TUI) exits with error when it finds a sample of
> > > zero length symbol(i.e. addr == sym->start == sym->end). Actually
> > > these are valid samples. Don't exit TUI and show report with such
> > > symbols.
> > >
> > > Link: https://lkml.org/lkml/2016/10/8/189
>
> You can add:
>
> Tested-by: Anton Blanchard <anton@samba.org>
>
> Also, since this issue makes perf report pretty much useless on
> ppc64, can we mark it for stable@, at least to get it into 4.9 where
> the ppc64 kernel changes that triggered this appeared?
Ok, added it, will be in the next pull req to Ingo.
- Arnaldo
> Anton
>
> > > Reported-by: Anton Blanchard <anton@samba.org>
> > > Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
> > > ---
> > > tools/perf/util/annotate.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c
> > > index aeb5a44..430d039 100644
> > > --- a/tools/perf/util/annotate.c
> > > +++ b/tools/perf/util/annotate.c
> > > @@ -593,7 +593,8 @@ static int __symbol__inc_addr_samples(struct
> > > symbol *sym, struct map *map,
> > >
> > > pr_debug3("%s: addr=%#" PRIx64 "\n", __func__,
> > > map->unmap_ip(map, addr));
> > >
> > > - if (addr < sym->start || addr >= sym->end) {
> > > + if ((addr < sym->start || addr >= sym->end) &&
> > > + (addr != sym->end || sym->start != sym->end)) {
> > > pr_debug("%s(%d): ERANGE! sym->name=%s, start=%#"
> > > PRIx64 ", addr=%#" PRIx64 ", end=%#" PRIx64 "\n", __func__,
> > > __LINE__, sym->name, sym->start, addr, sym->end); return -ERANGE;
> >
prev parent reply other threads:[~2016-12-19 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161121172818.161639c2@kryten>
[not found] ` <1479804050-5028-1-git-send-email-ravi.bangoria@linux.vnet.ibm.com>
2016-12-16 10:38 ` [PATCH] perf TUI: Don't throw error for zero length symbols Ravi Bangoria
2016-12-16 20:27 ` Anton Blanchard
2016-12-19 18:15 ` Arnaldo Carvalho de Melo [this message]
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=20161219181517.GA551@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=anton@samba.org \
--cc=chris.ryder@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masriniv@in.ibm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.vnet.ibm.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).