Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752516AbdFOLQl convert rfc822-to-8bit (ORCPT ); Thu, 15 Jun 2017 07:16:41 -0400 Received: from wildebeest.demon.nl ([212.238.236.112]:55672 "EHLO gnu.wildebeest.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752151AbdFOLQk (ORCPT ); Thu, 15 Jun 2017 07:16:40 -0400 Message-ID: <1497525392.3755.307.camel@klomp.org> Subject: Re: [PATCH v2] perf: libdw support for powerpc [ping] From: Mark Wielaard To: Milian Wolff Cc: Ravi Bangoria , Paolo Bonzini , linux-kernel@vger.kernel.org, acme@kernel.org, "Naveen N. Rao" , linuxppc-dev@lists.ozlabs.org Date: Thu, 15 Jun 2017 13:16:32 +0200 In-Reply-To: <3621613.kMnvz8Tm3d@milian-kdab2> References: <1496312681-20133-1-git-send-email-pbonzini@redhat.com> <1497354282.3755.201.camel@klomp.org> <59400ADD.4090709@linux.vnet.ibm.com> <3621613.kMnvz8Tm3d@milian-kdab2> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Mailer: Evolution 3.12.11 (3.12.11-22.el7) Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1413 Lines: 39 On Thu, 2017-06-15 at 10:46 +0200, Milian Wolff wrote: > Just a quick question: Have you guys applied my recent patch: > > commit 5ea0416f51cc93436bbe497c62ab49fd9cb245b6 > Author: Milian Wolff > 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. Thanks! No, I didn't have that patch (*) yet. It makes a huge difference. With that, Paolo's patch and the elfutils libdw powerpc64 fallback unwinder patch, it looks like I get user stack traces for everything now on ppc64le. Cheers, Mark (*) It just this one-liner, but what a difference that makes: --- a/tools/perf/util/unwind-libdw.c +++ b/tools/perf/util/unwind-libdw.c @@ -224,7 +224,7 @@ int unwind__get_entries(unwind_entry_cb_t cb, void *arg, err = dwfl_getthread_frames(ui->dwfl, thread->tid, frame_callback, ui); - if (err && !ui->max_stack) + if (err && ui->max_stack != max_stack) err = 0; /*