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 X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 722C8C54E4A for ; Tue, 12 May 2020 10:14:30 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3F190206A3 for ; Tue, 12 May 2020 10:14:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="MLVU8zV+" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3F190206A3 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Content-Type: Content-Transfer-Encoding:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=W5e0OUkAWO23OWOpemWYPHl4obKHbvd0B2dSyot54co=; b=MLVU8zV+ZcHQfaQVQu1Tpu8wp 4u6x6GddJmoWeCpIiRpIvCG8G4XOjh/QOBU6mbIlnGdaQ3XbJAunxESqF0mAzhIQgaaTGFk4Na79J cEsCahLNClPOqq4ZTteI0whcyuhyIL0VzX38Un8f8rDOhXlp/jx+32N1pf+35CgV/xpr7GbCNzzx9 l2MPPCaIL3X5AF5YnuwCtwKK62bETzf6PxRMsi+P0rTcaGaNnLCWY7+cLuPOtzc1Ky3sMywSjr2IO fcjYn2Vm9bcLm4U6+VMT4xj4SQx5wPNHy6pugdbvgHPt3VZ406pKDJJBqakgcQ/uOwq4X8RDyPArd et4IlMzSw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jYRvW-0006Gy-MA; Tue, 12 May 2020 10:14:18 +0000 Received: from lhrrgout.huawei.com ([185.176.76.210] helo=huawei.com) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jYRvS-0006G9-13 for linux-arm-kernel@lists.infradead.org; Tue, 12 May 2020 10:14:15 +0000 Received: from lhreml724-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id C703479D73E2140BD683; Tue, 12 May 2020 11:14:04 +0100 (IST) Received: from [127.0.0.1] (10.210.169.134) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 12 May 2020 11:14:03 +0100 Subject: Re: [PATCH RFC v3 00/12] perf pmu-events: Support event aliasing for system PMUs To: Joakim Zhang , "peterz@infradead.org" , "mingo@redhat.com" , "acme@kernel.org" , "mark.rutland@arm.com" , "alexander.shishkin@linux.intel.com" , "jolsa@redhat.com" , "namhyung@kernel.org" References: <1588852671-61996-1-git-send-email-john.garry@huawei.com> From: John Garry Message-ID: <2642e2a6-9e44-79c4-2bf5-498cedd897a4@huawei.com> Date: Tue, 12 May 2020 11:13:11 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Originating-IP: [10.210.169.134] X-ClientProxiedBy: lhreml733-chm.china.huawei.com (10.201.108.84) To lhreml724-chm.china.huawei.com (10.201.108.75) X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200512_031414_263827_529D7732 X-CRM114-Status: GOOD ( 12.69 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "irogers@google.com" , "ak@linux.intel.com" , "will@kernel.org" , Linuxarm , "linux-kernel@vger.kernel.org" , Zhangshaokun , "robin.murphy@arm.com" , "linux-arm-kernel@lists.infradead.org" Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org > I have an aside question, do you have any idea? Thanks a lot! > > For DDR PMU, I want to add bandwidth usage metric, but it depends on DDR controller clock frequency. > For example, we have i.MX8MM LPDDR4 board which DDR controller clock is 800MHZ, and i.MX8MM DDR4 board which DDR controller is 600MHZ, but the SoC is the same. > > So they can share all JSON metrics with identifier "i.mx8mm", except bandwidth metric. what is the bandwidth metric? how is it supposed to be calculated? If I add separate JOSN metrics files for identifier "i.mx8mm-lpddr4" and identifier "i.mx8mm-ddr4", then it's going to be very redundant, since most metrics are same just the identifier is different. > > Do you know how perf tool handle such case? jirka is supporting user-defined metric here: https://lore.kernel.org/lkml/20200511205307.3107775-1-jolsa@kernel.org/ So maybe you can use that somehow with separate scripts. Thanks, John _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel