Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp2243544rdb; Fri, 8 Dec 2023 02:31:33 -0800 (PST) X-Google-Smtp-Source: AGHT+IGJAs/OxBlDi1xULFoMWsm2L6xDbpEWmjivVwNDCgiMcJZasLApSyybdoMwWcXz13bmrdHN X-Received: by 2002:a17:90b:3145:b0:286:a04f:2833 with SMTP id ip5-20020a17090b314500b00286a04f2833mr3478554pjb.12.1702031492755; Fri, 08 Dec 2023 02:31:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702031492; cv=none; d=google.com; s=arc-20160816; b=lpVwILBxGv5wmrBxyK2xmQP/cLaOvdKGfzHutwrbhxOGMO1otZKnL4HTqRHFDRHvIs HDz2dQmG2jES+0anqpC+UT2+Y4pKVrT0sYSbS0a/w/YxMq/+xHWV1meXCATkLcUJDdx0 e79/mKxU60eDlhQ5qZ0Kx3DYsfYCpnjx6IXScIahbwdWgbJoidL6sNNHG1/k4wc/VfRr BVfTxbItA2dlzqo1YboukmXiG9MLIwCvGHH6fKhDdHfEMqu49JD10AdxONx2JHGs16Rd st5GVZER6Q67rVIv0xCssZu8gscUVWBJKzci2y1AbaqNXeNmgFmR3W72KUXKDdRscGSI Ud+g== 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-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=7qoKQ5iQtJ7ORKAjC/jbRnFF5PVRidwsUSKuUbzTiuc=; fh=ONqLW2f4gotRSTyBIKp0SnTrwjs/WnDlEqPKDjgAUqY=; b=y0cZ+CTVgu/Sg/AS/5U82tK6w/j6Cx8AUbDsUTJBrfbRH0axJltcF9rflrMijZQHuJ /66l3+uCeFw2v1X/3zX4st8ghGc//lR4CIQGQqTjJ6rOfy3waNPFDGnhi8O0Ub99stP1 KHsg9eEwJRLp/+J1VPvwzNRGTjhqOs4SanAMgr7Um9TYZDSrS8IK25sBNlbzwFZE852I MFaqzaCjeVdSGCOjW1JmAK47mm8NzKeBwCpHADcVUMuB+UtdECZZT57IkRCBlHxm9jae QCp9HLkiPrYqgEYPtintZ/7Zrg2r1XvTtLCVBi7xju80KeYBO+Bbc1/JrM+yV+LE4m3w MWMA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=wKNJgN6c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from groat.vger.email (groat.vger.email. [23.128.96.35]) by mx.google.com with ESMTPS id kx9-20020a17090b228900b002867c645d4bsi2733527pjb.13.2023.12.08.02.31.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 08 Dec 2023 02:31:32 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=wKNJgN6c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id EBECF8079C83; Fri, 8 Dec 2023 02:31:14 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1573652AbjLHKac (ORCPT + 99 others); Fri, 8 Dec 2023 05:30:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40134 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235876AbjLHKaH (ORCPT ); Fri, 8 Dec 2023 05:30:07 -0500 Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8D0102106 for ; Fri, 8 Dec 2023 02:29:31 -0800 (PST) Received: by mail-pl1-x630.google.com with SMTP id d9443c01a7336-1d0c4d84bf6so14260595ad.1 for ; Fri, 08 Dec 2023 02:29:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1702031371; x=1702636171; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=7qoKQ5iQtJ7ORKAjC/jbRnFF5PVRidwsUSKuUbzTiuc=; b=wKNJgN6c/ct0c7iwBrH1iRFQWXotLdF9N88tl0Ec48t0Uf6Sgh/0KRjCgWqvkPSAT3 edB5nd2MOPRfvsKWdXJN11Ne7Fm/NaTzoFXTbxnCbp8AbnHJLUWPNlxFo+SDSnJJyNaO 9c/iAskhpJniaSdPUHDe/j5CLZPjZ5DAWK7Y39nu8YwOB9IhInl5+5GwzDOvjMvHCUGj m7ISwxZtX3vNBCoVenUkUZTL6v5cuOfbvT5WNJiGgPMv9hyeoF3+L+u7exuURteU2gSt IHYqSBHnNMaol2uNU2GnTvO4BQVHYUKU4f01TrUMw5qAlfwaR1xdmVz+Q1NCj6RWwYEl iUGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702031371; x=1702636171; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=7qoKQ5iQtJ7ORKAjC/jbRnFF5PVRidwsUSKuUbzTiuc=; b=C0Z8iOWY1BV+W8PS72CqRmaPA39W53ug23MC8Bj/tgc6Ge1ZTX9wKTxvdMr7+WbCFe +8mfZTJDTu/V2Siv7RkxLlHwHsZIVO5cqYsmlUIHQ9rXeH7dh/BCHLY7qpMG7s4tcPyF X41UQuru9V+1FuemltdopXFkmD0S1Ejb9eiDWU4y/w3oi0FPwe7JUy5LppiDXnmV48xX kKrXh386OTUne4pQojphJC8WLVXA2F93c0yHywN9kYDChIyWlg02iTgKVxkNwq0tpCZg b71QMP0gWdN40T8se1zO3bxCpytH49gPipIJe1GHFg/1us/FenXQZneHbjAlvs/MGrHT 2erQ== X-Gm-Message-State: AOJu0YyGLQc1BVtoT+Is9QSy7P7NM8/2WKf5Kes8Zf96Mew4meHZF2HZ /oWvLGJJ18LlqWHOgg84h2mFtw== X-Received: by 2002:a17:903:1209:b0:1d0:cfdc:10cb with SMTP id l9-20020a170903120900b001d0cfdc10cbmr3805283plh.72.1702031370812; Fri, 08 Dec 2023 02:29:30 -0800 (PST) Received: from leoy-huanghe.lan ([94.177.131.71]) by smtp.gmail.com with ESMTPSA id j15-20020a170902da8f00b001c9db5e2929sm1357806plx.93.2023.12.08.02.29.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 08 Dec 2023 02:29:30 -0800 (PST) Date: Fri, 8 Dec 2023 18:29:22 +0800 From: Leo Yan To: kan.liang@linux.intel.com Cc: acme@kernel.org, irogers@google.com, peterz@infradead.org, mingo@redhat.com, namhyung@kernel.org, jolsa@kernel.org, adrian.hunter@intel.com, john.g.garry@oracle.com, will@kernel.org, james.clark@arm.com, mike.leach@linaro.org, yuhaixin.yhx@linux.alibaba.com, renyu.zj@linux.alibaba.com, tmricht@linux.ibm.com, ravi.bangoria@amd.com, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH V2 1/5] perf mem: Add mem_events into the supported perf_pmu Message-ID: <20231208102922.GB769184@leoy-huanghe.lan> References: <20231207192338.400336-1-kan.liang@linux.intel.com> <20231207192338.400336-2-kan.liang@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231207192338.400336-2-kan.liang@linux.intel.com> X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Fri, 08 Dec 2023 02:31:15 -0800 (PST) On Thu, Dec 07, 2023 at 11:23:34AM -0800, kan.liang@linux.intel.com wrote: > From: Kan Liang > > With the mem_events, perf doesn't need to read sysfs for each PMU to > find the mem-events-supported PMU. The patch also makes it possible to > clean up the related __weak functions later. > > The patch is only to add the mem_events into the perf_pmu for all ARCHs. > It will be used in the later cleanup patches. > > Reviewed-by: Ian Rogers > Tested-by: Ravi Bangoria > Signed-off-by: Kan Liang > --- > tools/perf/arch/arm64/util/mem-events.c | 4 ++-- > tools/perf/arch/arm64/util/mem-events.h | 7 +++++++ > tools/perf/arch/arm64/util/pmu.c | 6 ++++++ > tools/perf/arch/s390/util/pmu.c | 3 +++ > tools/perf/arch/x86/util/mem-events.c | 4 ++-- > tools/perf/arch/x86/util/mem-events.h | 9 +++++++++ > tools/perf/arch/x86/util/pmu.c | 7 +++++++ > tools/perf/util/mem-events.c | 2 +- > tools/perf/util/mem-events.h | 1 + > tools/perf/util/pmu.c | 4 +++- > tools/perf/util/pmu.h | 7 +++++++ > 11 files changed, 48 insertions(+), 6 deletions(-) > create mode 100644 tools/perf/arch/arm64/util/mem-events.h > create mode 100644 tools/perf/arch/x86/util/mem-events.h > > diff --git a/tools/perf/arch/arm64/util/mem-events.c b/tools/perf/arch/arm64/util/mem-events.c > index 3bcc5c7035c2..aaa4804922b4 100644 > --- a/tools/perf/arch/arm64/util/mem-events.c > +++ b/tools/perf/arch/arm64/util/mem-events.c > @@ -4,7 +4,7 @@ > > #define E(t, n, s) { .tag = t, .name = n, .sysfs_name = s } > > -static struct perf_mem_event perf_mem_events[PERF_MEM_EVENTS__MAX] = { > +struct perf_mem_event perf_mem_events_arm[PERF_MEM_EVENTS__MAX] = { > E("spe-load", "arm_spe_0/ts_enable=1,pa_enable=1,load_filter=1,store_filter=0,min_latency=%u/", "arm_spe_0"), > E("spe-store", "arm_spe_0/ts_enable=1,pa_enable=1,load_filter=0,store_filter=1/", "arm_spe_0"), > E("spe-ldst", "arm_spe_0/ts_enable=1,pa_enable=1,load_filter=1,store_filter=1,min_latency=%u/", "arm_spe_0"), > @@ -17,7 +17,7 @@ struct perf_mem_event *perf_mem_events__ptr(int i) > if (i >= PERF_MEM_EVENTS__MAX) > return NULL; > > - return &perf_mem_events[i]; > + return &perf_mem_events_arm[i]; I recognized that it's hard code to "arm_spe_0", which might break if system registers different Arm SPE groups. But this is not the issue introduced by this patch, we might need to consider to fix it later. > } > > const char *perf_mem_events__name(int i, const char *pmu_name __maybe_unused) > diff --git a/tools/perf/arch/arm64/util/mem-events.h b/tools/perf/arch/arm64/util/mem-events.h > new file mode 100644 > index 000000000000..5fc50be4be38 > --- /dev/null > +++ b/tools/perf/arch/arm64/util/mem-events.h > @@ -0,0 +1,7 @@ > +/* SPDX-License-Identifier: GPL-2.0 */ > +#ifndef _ARM64_MEM_EVENTS_H > +#define _ARM64_MEM_EVENTS_H > + > +extern struct perf_mem_event perf_mem_events_arm[PERF_MEM_EVENTS__MAX]; > + > +#endif /* _ARM64_MEM_EVENTS_H */ > diff --git a/tools/perf/arch/arm64/util/pmu.c b/tools/perf/arch/arm64/util/pmu.c > index 2a4eab2d160e..06ec9b838807 100644 > --- a/tools/perf/arch/arm64/util/pmu.c > +++ b/tools/perf/arch/arm64/util/pmu.c > @@ -8,6 +8,12 @@ > #include > #include > > +void perf_pmu__arch_init(struct perf_pmu *pmu) > +{ > + if (!strcmp(pmu->name, "arm_spe_0")) > + pmu->mem_events = perf_mem_events_arm; This is not right and it should cause building failure on aarch64. aarch64 reuses aarch32's file arch/arm/util/pmu.c, and this file has already defined perf_pmu__arch_init(), you should add above change in the file arch/arm/util/pmu.c. Now I cannot access a machine for testing Arm SPE, but I will play a bit for this patch set to ensure it can pass compilation. After that, I will seek Arm maintainers/reviewers help for the test. Thanks, Leo