Received: by 2002:a05:6358:53a8:b0:117:f937:c515 with SMTP id z40csp4737707rwe; Mon, 17 Apr 2023 18:19:18 -0700 (PDT) X-Google-Smtp-Source: AKy350aj2m9EKxld5MzKu3HbYnMRtopN2ZxHIU7cbLzJPKmxJYnCw4B4IjTKcJKvn9pxYWakND4H X-Received: by 2002:a17:90a:a681:b0:247:a3e8:a9cd with SMTP id d1-20020a17090aa68100b00247a3e8a9cdmr378372pjq.24.1681780758421; Mon, 17 Apr 2023 18:19:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681780758; cv=none; d=google.com; s=arc-20160816; b=DHj25uRNwpB7siWi4a1eD8+ZJCinRldO86p0RsGmKkD9WEkw3xq8gHRH3mThVePpyJ tNEQnbKocDdzfATD3/GGRVry1+To0hjP8oMiMyfeYB5zZDVBZxaynMAROoTyPnRABnKZ K4a5jb3Bln/+pwiTVlbxMG3a1Ot2MsBIdt/VfoXyYkq4Kw1fN5JvVmg0vf7Oxne8dO6l 9mJd6MZQZXBalL13n/Gk1NJTI1p9YcYSm/bcUG8+VERdc/EZ6cf/hO0StssPPexA3qDN Tm/p+t7/Yub6BY7n8ystJST3jWZ0afynAC+jXacTNnsiGP0V7fcCkm1m66qO0fo53dzF XLEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=9zWHRMOjUVmVOBV8FAVMVO7pYC38PvfpWDrmP4YP890=; b=eur69q9z7VW30DrSO0UmfKOcZm/sSvqnQ3cCGCR79rhIWMy54k9XhGTWgYRO3P2kui +Q/UZxgSS2vdz0WmfCDMz5n3NmQGhdwORx3PM70cbfU+HR8pRVVx6kQrhHgrMN3R27Dh v43mygyFWG7XJnsI+miJMpVHV2Gtg3bJ4KyqWZW/2sYKDu5Fz8FOb5Li+xHQ3bqDjKtL 7QV3qPgyIH3GU2ngG8Fo+v+JDWGEuM9Pb4+CqE+lV0An/F1BtdXDyXDkcmjONDVnvNhV 6EhrxDhWwdPBhmSOxhc6mNtz7glTDZUwKSebmJJrhDXQtJSA5eFoa1eNjnjJidwTnM2f lpXQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=ManG2OfN; 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=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x64-20020a638643000000b0051f6fab06bfsi46385pgd.709.2023.04.17.18.19.07; Mon, 17 Apr 2023 18:19:18 -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=@kernel.org header.s=k20201202 header.b=ManG2OfN; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230217AbjDRBPJ (ORCPT + 99 others); Mon, 17 Apr 2023 21:15:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40154 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229619AbjDRBPH (ORCPT ); Mon, 17 Apr 2023 21:15:07 -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 C40A83C0D; Mon, 17 Apr 2023 18:15:06 -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 EAC9E6182F; Tue, 18 Apr 2023 01:15:05 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5FBAAC433A7; Tue, 18 Apr 2023 01:15:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1681780505; bh=jsS1F46hAQbhHVpD+vXSY2C2u6Z+ww/kmcB8nSA4RKg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=ManG2OfNtk/zGAtRVUTd1eGyebp0k9xtlGagHt9sOeG/HWiCDHWd28EPCXQb2dezj GldNZndaDjzYwt/1u5nPVrKt0qc1ZM7/76yzJYzWOcHfhq5kYwNt9webhWCzDT6Pjp 4j4ZrIwaB4cCeaCmA7I/rPy4ObCLcDKbmFM+5CaVi8CjJm90Fi24gHVft5vb3ddy27 igvJZfYVxw+HatzH7KVV8kK0dMf8yWhtHMxdY76uJqpv67HR63uYvfWU8q0TirYFbw LyCjV05r+NZmNFlcIlMJathLXomrf8S6lhklYMsy02NwZJIryFntYba8okwDI3hshh +90IzBVz4R4kA== Received: by mail-ej1-f46.google.com with SMTP id a5so12504296ejb.6; Mon, 17 Apr 2023 18:15:05 -0700 (PDT) X-Gm-Message-State: AAQBX9dfnWMGB9xAndXLEGsFA/tfGo4DmcppWbly+QZpK9P6L9C8csAu 9RYW4356S00uNld//tVugRP38b3tpBg3JsDT+94= X-Received: by 2002:a17:906:5e12:b0:92d:878e:8566 with SMTP id n18-20020a1709065e1200b0092d878e8566mr4631793eju.10.1681780503472; Mon, 17 Apr 2023 18:15:03 -0700 (PDT) MIME-Version: 1.0 References: <20230410111823.2538831-1-chenhuacai@loongson.cn> <0a278ab5-751a-9433-3d1f-19a5a6b99d39@loongson.cn> In-Reply-To: From: Huacai Chen Date: Tue, 18 Apr 2023 09:14:51 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH V2] tools/perf: Add basic support for LoongArch To: Youling Tang Cc: Huacai Chen , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , loongarch@lists.linux.dev, Xuefeng Li , Tiezhu Yang , Xuerui Wang , linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, loongson-kernel@lists.loongnix.cn, Ming Wang Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham 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 Mon, Apr 17, 2023 at 5:22=E2=80=AFPM Youling Tang wrote: > > /* snip */ > > >>>> --- /dev/null > >>>> +++ b/tools/perf/arch/loongarch/util/dwarf-regs.c > >>>> @@ -0,0 +1,44 @@ > >>>> +// SPDX-License-Identifier: GPL-2.0 > >>>> +/* > >>>> + * dwarf-regs.c : Mapping of DWARF debug register numbers into > >>>> register names. > >>>> + * > >>>> + * Copyright (C) 2020-2023 Loongson Technology Corporation Limited > >>>> + */ > >>>> + > >>>> +#include > >>>> +#include /* for EINVAL */ > >>>> +#include /* for strcmp */ > >>>> +#include > >>>> + > >>>> +struct pt_regs_dwarfnum { > >>>> + const char *name; > >>>> + unsigned int dwarfnum; > >>>> +}; > >>>> + > >>>> +static struct pt_regs_dwarfnum loongarch_gpr_table[] =3D { > >>>> + {"$0", 0}, {"$1", 1}, {"$2", 2}, {"$3", 3}, > >>>> + {"$4", 4}, {"$5", 5}, {"$6", 6}, {"$7", 7}, > >>>> + {"$8", 8}, {"$9", 9}, {"$10", 10}, {"$11", 11}, > >>>> + {"$12", 12}, {"$13", 13}, {"$14", 14}, {"$15", 15}, > >>>> + {"$16", 16}, {"$17", 17}, {"$18", 18}, {"$19", 19}, > >>>> + {"$20", 20}, {"$21", 21}, {"$22", 22}, {"$23", 23}, > >>>> + {"$24", 24}, {"$25", 25}, {"$26", 26}, {"$27", 27}, > >>>> + {"$28", 28}, {"$29", 29}, {"$30", 30}, {"$31", 31}, > >>>> + {NULL, 0} > >>>> +}; > >>> Do you need to change it to the following: > >>> > >>> #define GPR_DWARFNUM_NAME(num) {.name =3D __stringify($r##num), .dwar= fnum > >>> =3D num} > >>> #define REG_DWARFNUM_END {.name =3D NULL, .dwarfnum =3D 0} > >>> > >>> static const struct pt_regs_dwarfnum regdwarfnum_table[] =3D { > >>> GPR_DWARFNUM_NAME(0), > >>> GPR_DWARFNUM_NAME(1), > >>> GPR_DWARFNUM_NAME(2), > >>> GPR_DWARFNUM_NAME(3), > >>> GPR_DWARFNUM_NAME(4), > >>> GPR_DWARFNUM_NAME(5), > >>> GPR_DWARFNUM_NAME(6), > >>> GPR_DWARFNUM_NAME(7), > >>> GPR_DWARFNUM_NAME(8), > >>> GPR_DWARFNUM_NAME(9), > >>> GPR_DWARFNUM_NAME(10), > >>> GPR_DWARFNUM_NAME(11), > >>> GPR_DWARFNUM_NAME(12), > >>> GPR_DWARFNUM_NAME(13), > >>> GPR_DWARFNUM_NAME(14), > >>> GPR_DWARFNUM_NAME(15), > >>> GPR_DWARFNUM_NAME(16), > >>> GPR_DWARFNUM_NAME(17), > >>> GPR_DWARFNUM_NAME(18), > >>> GPR_DWARFNUM_NAME(19), > >>> GPR_DWARFNUM_NAME(20), > >>> GPR_DWARFNUM_NAME(21), > >>> GPR_DWARFNUM_NAME(22), > >>> GPR_DWARFNUM_NAME(23), > >>> GPR_DWARFNUM_NAME(24), > >>> GPR_DWARFNUM_NAME(25), > >>> GPR_DWARFNUM_NAME(26), > >>> GPR_DWARFNUM_NAME(27), > >>> GPR_DWARFNUM_NAME(28), > >>> GPR_DWARFNUM_NAME(29), > >>> REG_DWARFNUM_NAME(30), > >>> REG_DWARFNUM_NAME(31), > >>> REG_DWARFNUM_END, > >>> }; > >>> > >>> At the same time, "$rx" is used in __perf_reg_name_loongarch and > >>> loongarch_regstr_tbl, which is consistent with assembly. > >> OK, I will use the "$rx" format, but I don't want to use macros. > > Use the "rx" format to make regs_query_register_offset consistent with > > arch/loongarch/kernel/ptrace.c (that is, the names in > > loongarch_gpr_table and regoffset_table are consistent) > > If we want to be consistent with the usage of `trace probe`, we should > use "%rx". OK, make sense. Huacai > > eg: > # echo "p:myuprobe /tmp/test:0x4194 %r4 %r5" > uprobe_events > > parse_probe_arg() > case '%': regs_query_register_offset() > > Youling. > > > > Youling. > >> > >> Huacai > >>> > >>>> + > >>>> +const char *get_arch_regstr(unsigned int n) > >>>> +{ > >>>> + n %=3D 32; > >>>> + return loongarch_gpr_table[n].name; > >>>> +} > >>>> + > >>>> +int regs_query_register_offset(const char *name) > >>>> +{ > >>>> + const struct pt_regs_dwarfnum *roff; > >>>> + > >>>> + for (roff =3D loongarch_gpr_table; roff->name !=3D NULL; roff+= +) > >>>> + if (!strcmp(roff->name, name)) > >>>> + return roff->dwarfnum; > >>>> + return -EINVAL; > >>>> +} > > > >