From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
Mark Wielaard <mark@klomp.org>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] perf: libdw support for powerpc [ping]
Date: Tue, 20 Jun 2017 22:07:39 -0300 [thread overview]
Message-ID: <20170621010739.GL13640@kernel.org> (raw)
In-Reply-To: <3621613.kMnvz8Tm3d@milian-kdab2>
Em Thu, Jun 15, 2017 at 10:46:16AM +0200, Milian Wolff escreveu:
> On Tuesday, June 13, 2017 5:55:09 PM CEST Ravi Bangoria wrote:
> Just a quick question: Have you guys applied my recent patch:
> commit 5ea0416f51cc93436bbe497c62ab49fd9cb245b6
> Author: Milian Wolff <milian.wolff@kdab.com>
> Date: Thu Jun 1 23:00:21 2017 +0200
> perf report: Include partial stacks unwound with libdw
> So far the whole stack was thrown away when any error occurred before
> the maximum stack depth was unwound. This is actually a very common
> scenario though. The stacks that got unwound so far are still
> interesting. This removes a large chunk of differences when comparing
> perf script output for libunwind and libdw perf unwinding.
>
> If not, then this could explain the issue you are seeing.
Hi Millian, can I take this as an Acked-by or Tested-by?
- Arnaldo
next prev parent reply other threads:[~2017-06-21 1:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 10:24 [PATCH v2] perf: libdw support for powerpc Paolo Bonzini
2017-06-09 12:30 ` [PATCH v2] perf: libdw support for powerpc [ping] Paolo Bonzini
2017-06-12 11:58 ` Ravi Bangoria
2017-06-13 11:44 ` Mark Wielaard
2017-06-13 11:44 ` Mark Wielaard
2017-06-13 15:55 ` Ravi Bangoria
2017-06-15 8:46 ` Milian Wolff
2017-06-15 11:16 ` Mark Wielaard
2017-06-15 11:16 ` Mark Wielaard
2017-06-16 4:21 ` Ravi Bangoria
2017-06-21 1:06 ` Arnaldo Carvalho de Melo
2017-06-21 1:31 ` Mark Wielaard
2017-06-21 1:07 ` Arnaldo Carvalho de Melo [this message]
2017-06-21 8:16 ` Milian Wolff
2017-06-21 12:48 ` Arnaldo Carvalho de Melo
2017-06-21 14:19 ` Milian Wolff
2017-06-21 14:33 ` Arnaldo Carvalho de Melo
2017-06-15 12:13 ` [PATCH v2] perf: libdw support for powerpc Jiri Olsa
2017-06-20 21:53 ` Arnaldo Carvalho de Melo
2017-06-21 18:19 ` [tip:perf/core] perf unwind: Support " tip-bot for Paolo Bonzini
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=20170621010739.GL13640@kernel.org \
--to=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark@klomp.org \
--cc=milian.wolff@kdab.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--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 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.