From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 12902C76188 for ; Mon, 3 Apr 2023 20:30:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232405AbjDCUaq (ORCPT ); Mon, 3 Apr 2023 16:30:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46720 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231185AbjDCUao (ORCPT ); Mon, 3 Apr 2023 16:30:44 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ABACE422B; Mon, 3 Apr 2023 13:30:20 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 03F1E62A81; Mon, 3 Apr 2023 20:30:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2833BC4339B; Mon, 3 Apr 2023 20:30:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1680553819; bh=u9ctzmotB7LsdpoZe69ltNDwwwg7R0/ol4MkFQo5CfQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=GEVSS5fC29vNmENJS9yYCujKVQY4UUkITZkXxUlNx02f0leRK34jiLQ8dyuNwhbsJ AAovnVl9HhUrJ+w2MEM11+r1H8AED0uszqdzwWklzIb4YyOfvMSB7XFXONpnJgzvOq L6nQgA0soVixsgdruEdmlx29U+KhaJOXaxvANZdR00bUap599/ZL4DqnVemz6ouNUK 8pW3DEQXUyiIKYxRkPuYCo/lZow3IYYcBczlwfbbhQgBxFj7lIDvQhq/Tu0XBvuicN Bco9D/6Ld3aqHjA0q0NI6vxsg4I7BhCbkw93rEQvBzjj9/w1BBufKK+2Ee4Qm1Shxe ibTY9EPE/4Sbg== Received: by quaco.ghostprotocols.net (Postfix, from userid 1000) id 1560C4052D; Mon, 3 Apr 2023 17:30:17 -0300 (-03) Date: Mon, 3 Apr 2023 17:30:17 -0300 From: Arnaldo Carvalho de Melo To: Artem Savkov Cc: Adrian Hunter , Namhyung Kim , Peter Zijlstra , Ingo Molnar , Mark Rutland , Alexander Shishkin , Jiri Olsa , Ian Rogers , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, Milian Wolff , Masami Hiramatsu , Andrii Nakryiko Subject: Re: [PATCH 0/1] perf report: append inlines to non-dwarf callchains Message-ID: References: <20230316133557.868731-1-asavkov@redhat.com> <8f7077e8-bcce-a13f-48d3-92a3cb80b02a@intel.com> <20230331085224.GA688995@samus.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20230331085224.GA688995@samus.usersys.redhat.com> X-Url: http://acmel.wordpress.com Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Fri, Mar 31, 2023 at 10:52:24AM +0200, Artem Savkov escreveu: > On Thu, Mar 30, 2023 at 08:06:20AM +0300, Adrian Hunter wrote: > > On 22/03/23 21:44, Arnaldo Carvalho de Melo wrote: > > > Em Wed, Mar 22, 2023 at 11:18:49AM -0700, Namhyung Kim escreveu: > > >> On Fri, Mar 17, 2023 at 12:41 AM Artem Savkov wrote: > > >>> > > >>> On Thu, Mar 16, 2023 at 02:26:18PM -0700, Namhyung Kim wrote: > > >>>> Hello, > > >>>> > > >>>> On Thu, Mar 16, 2023 at 6:36 AM Artem Savkov wrote: > > >>>>> > > >>>>> In an email to Arnaldo Andrii Nakryiko suggested that perf can get > > >>>>> information about inlined functions from dwarf when available and then > > >>>>> add it to userspace stacktraces even in framepointer or lbr mode. > > >>>>> Looking closer at perf it turned out all required bits and pieces are > > >>>>> already there and inline information can be easily added to both > > >>>>> framepointer and lbr callchains by adding an append_inlines() call to > > >>>>> add_callchain_ip(). > > >>>> > > >>>> Looks great! Have you checked it with perf report -g callee ? > > >>>> I'm not sure the ordering of inlined functions is maintained > > >>>> properly. Maybe you can use --no-children too to simplify > > >>>> the output. > > >>> > > >>> Thanks for the suggestion. I actually have another test program with > > >>> functions being numbered rather than (creatively) named, so it might be > > >>> easier to use it to figure out ordering. Here's the code: > > >> > > >> Yep, looks good. > > >> > > >> Acked-by: Namhyung Kim > > > > > > So, I'll apply this shorter patch instead, ok? > > > > > > - Arnaldo > > > > > > diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c > > > index 803c9d1803dd26ef..abf6167f28217fe6 100644 > > > --- a/tools/perf/util/machine.c > > > +++ b/tools/perf/util/machine.c > > > @@ -44,6 +44,7 @@ > > > #include > > > > > > static void __machine__remove_thread(struct machine *machine, struct thread *th, bool lock); > > > +static int append_inlines(struct callchain_cursor *cursor, struct map_symbol *ms, u64 ip); > > > > > > static struct dso *machine__kernel_dso(struct machine *machine) > > > { > > > @@ -2322,6 +2323,10 @@ static int add_callchain_ip(struct thread *thread, > > > ms.maps = al.maps; > > > ms.map = al.map; > > > ms.sym = al.sym; > > > + > > > + if (append_inlines(cursor, &ms, ip) == 0) > > > + return 0; > > > + > > > srcline = callchain_srcline(&ms, al.addr); > > > return callchain_cursor_append(cursor, ip, &ms, > > > branch, flags, nr_loop_iter, > > > > This seems to be breaking --branch-history. I am not sure > > append_inlines() makes sense for branches. Maybe this should be: > > > > if (!branch && !append_inlines(cursor, &ms, ip)) > > return 0; > > > > Right. So when cllchain_cursor is appended through append_inlines it > always discards branch information, even for the non-inlined function. > So adding !branch makes sense to me. Does anyone else see any problems > with that? I'm no expert in this specific area, so for now till we get to a conclusion on this, I'll follow Andi's suggestion and revert this patch. - Arnaldo