Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp768503rwl; Fri, 31 Mar 2023 02:01:19 -0700 (PDT) X-Google-Smtp-Source: AKy350Yek7hj6DKPE+Syw0qjbFPpB6a7I6ibY1fhn2Y1H7IOXgAiDFON65+uP4zgpL6YWCws+CgI X-Received: by 2002:a17:902:aa8a:b0:1a0:4405:5787 with SMTP id d10-20020a170902aa8a00b001a044055787mr5529021plr.0.1680253279306; Fri, 31 Mar 2023 02:01:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680253279; cv=none; d=google.com; s=arc-20160816; b=Mp6MHIry9Jno6OGxmwz/wjsMgQkWIHaogYqkZxR2fVIJB5TL/T6acYNNCy2BLjiSQT rHt0qd0faRR1i4qaZNnMZbt/GX7xRooc4xh+V6Au3frWcNgoQRw1mcJIl+P3u5WUJGSW VD6MBKjQ06uE2rc7AqoT9IG8Z8EvHhJhOmzzsDSg/NjTH2n6yuaFUCwBCaZHOov7Vklk xyxAryI3+UiOu8AVjslOSvQEXPTUqJFdYMpiiRd8lIL6gRdZM7SuuWoaAwzoGYk08XOI gmoSeX0Br247WWpucYrpHTFPQldwuRdFU5s5XgAA3UJ026ids742gGSJK6Fe96GFPzOX oaNA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=NvLw4mvzyoe66j5YooKZQUM0RLq2l1MwiNMdbPsqMr8=; b=xlXUXAx9hXHHvn8+z2+GIrBW7eSZzxZJ/tx5DW2W2bV7oXrMgGP404rSVI5Knxh7VD xyzODFz7xkLYrHFVV7NoHqZuKCtQpRC8zWDZta9w5YIRuLseRPBd/gmIbCVA7BqaHVVJ c4KiXa5U624kJAceSrlgD1cQZckIwnlOAtLm8ezqYqSI4kTdxcxbZeC4LoaG7vFzER5P EvVw/h/kmXYkcQyejTrLD5BKSvlHZX83SBQo1ldlYOPoaRAaVOz9ACOselQQryIVRkFV Cq3aPGBFWW8+DorhUve3WuqxPJCjuGZlYtlgnCbrHrYycZlpsPZiRoevczFPhIcvO43C 2y+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=QuXGKX5T; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m18-20020a170902db1200b001a1e867f287si1755068plx.460.2023.03.31.02.01.05; Fri, 31 Mar 2023 02:01:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=QuXGKX5T; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231362AbjCaIxX (ORCPT + 99 others); Fri, 31 Mar 2023 04:53:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60304 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230007AbjCaIxW (ORCPT ); Fri, 31 Mar 2023 04:53:22 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3EC565BAD for ; Fri, 31 Mar 2023 01:52:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680252755; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=NvLw4mvzyoe66j5YooKZQUM0RLq2l1MwiNMdbPsqMr8=; b=QuXGKX5Tpepi/JqY4eZM7xHIW9eu2cawDpGcTq7yke4S6iOK4nWlb2dqlKAALe4R1L+0f3 KfHudHLNn5KmjKq7xEvP0Ffx1jhoAzUhJF7CQ4ct4N7p9NFntZlw11aqRqiO8WMZF2c/z2 HH885rynjsRFgFBlXHJoQ06kLz8vFRg= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-278-ku1Ytj2hPFuhoEakXWNdcg-1; Fri, 31 Mar 2023 04:52:29 -0400 X-MC-Unique: ku1Ytj2hPFuhoEakXWNdcg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 7326A855300; Fri, 31 Mar 2023 08:52:28 +0000 (UTC) Received: from samus.usersys.redhat.com (unknown [10.43.17.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 626D14042AC5; Fri, 31 Mar 2023 08:52:26 +0000 (UTC) Date: Fri, 31 Mar 2023 10:52:24 +0200 From: Artem Savkov To: Adrian Hunter Cc: Arnaldo Carvalho de Melo , 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: <20230331085224.GA688995@samus.usersys.redhat.com> References: <20230316133557.868731-1-asavkov@redhat.com> <8f7077e8-bcce-a13f-48d3-92a3cb80b02a@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8f7077e8-bcce-a13f-48d3-92a3cb80b02a@intel.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? -- Artem