Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp89412pxb; Mon, 8 Nov 2021 10:13:01 -0800 (PST) X-Google-Smtp-Source: ABdhPJwD0z03U2YNjv9U1Vlk36l2W8aE461gIYXxv83beemgIn3aRUz0yI+d6IulFP5PboLW30QM X-Received: by 2002:a6b:7a06:: with SMTP id h6mr735544iom.128.1636395181452; Mon, 08 Nov 2021 10:13:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1636395181; cv=none; d=google.com; s=arc-20160816; b=VTbc3RTaRCIo4ukKZZdAMueq5Rxv1XP60C+Y2O4kTvu/8BLVgzy2Ib+woXAkTMwDUK t5rBEQvuxm2fqH16XI1WMWN9RATdJ30M0DDzWI2OHehfOuZ7cgIFn3C4DfLcUrP9tmVk nmYDMRkmI2MZGZP4XBZ01wCL2RPFt6DKDiCpElYbl8m2iOmGLaAasM4ie4nAjrPWOV/b bFdLwrzL92pM1X195cVl6TRm1S/iEj2J0Nre+5TR5f0RSPI+Re7urS6i8MEpUDKtRCnB BvIfLkB4koGPHY3K2oEL0xpjbIZDxDUF1xetwLitUPgW9co7S6ut6ELIEFTrQYyqbHWM Mt7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:cc :references:to:subject; bh=HKhlvZnrGq4neUwfhrWxImg79qGeA2Cvwntf6HpksP8=; b=XvE2k3nH5sKQ7a+wDasimxGtCT5WMbeMgC6MGyt5JVGraWndhOCHiA4fkTpG61/L5G hcYvoLsnWPKiU2LWBFf0yXsOHkE/iXYBqLwaPMNQCYMyTbps2b6CZ92hnXn/7e3CaxoI J/BG/1dfYvK1rZZqxXUbPadvIEuNCZCjhOxQBTKg2bFXMZNoHlA++FjnlFA4zjSN8R2M 3mdjyIblVCji4spcV7y7AZem+QG4ZlMuiJ4FSsMBvjIOZlqQWWTwOffuaO2p7wjFdccp wQ+mafo1YqodzhCjuABna3tFqsMMspi/ia9eVxtMZN4ytJLjk8NtfN0cHXJAACRs5Rx0 TVXA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k12si32836093iov.104.2021.11.08.10.12.48; Mon, 08 Nov 2021 10:13:01 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239570AbhKHMoe (ORCPT + 99 others); Mon, 8 Nov 2021 07:44:34 -0500 Received: from frasgout.his.huawei.com ([185.176.79.56]:4068 "EHLO frasgout.his.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231529AbhKHMod (ORCPT ); Mon, 8 Nov 2021 07:44:33 -0500 Received: from fraeml713-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4HnrGR6WVJz67Lng; Mon, 8 Nov 2021 20:37:03 +0800 (CST) Received: from lhreml724-chm.china.huawei.com (10.201.108.75) by fraeml713-chm.china.huawei.com (10.206.15.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Mon, 8 Nov 2021 13:41:47 +0100 Received: from [10.47.92.13] (10.47.92.13) 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.2308.15; Mon, 8 Nov 2021 12:41:47 +0000 Subject: Re: Question: SMMUv3 PMU event aliasing To: Leo Yan , , References: <20211108121941.GC1267967@leoy-ThinkPad-X240s> CC: "linux-arm-kernel@lists.infradead.org" From: John Garry Message-ID: <8b24f36b-6459-c13c-bf19-b9f588eb6b8e@huawei.com> Date: Mon, 8 Nov 2021 12:41:33 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: <20211108121941.GC1267967@leoy-ThinkPad-X240s> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.47.92.13] X-ClientProxiedBy: lhreml748-chm.china.huawei.com (10.201.108.198) To lhreml724-chm.china.huawei.com (10.201.108.75) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/11/2021 12:19, Leo Yan wrote: > Hi John, > > [ + mailing list ] Hi Leo, > > I'd like to confirm the latest upstream status for SMMUv3 PMU event > aliasing. > > I see the patch set v6 of "perf pmu-events: Support event aliasing for > system PMUs" [1] has been landed on the mainline kernel, and as an > example, imx8mm DDR PMU has been supported as system PMU [2]. > > On the other hand, I can see patch set 5 contains the SMMUv3 PMU event > aliasing with patch "perf vendor events arm64: Add Architected events > smmuv3-pmcg.json" [3], but this patch was left out in patch set 6 and > it's never landed on the mainline kernel. > > Could you share current status (or plan) for upstreaming SMMUv3 PMU > event alias? Or if there have any block issue to prevent merging the > changes in the mainline kernel? This feature should be supported in the SMMUv3 PMU kernel driver and perf tool. However it relies on the SMMU PMU identifier sysfs file to work. This relies on SMMU_PMCG_IIDR being set, which is introduced latest spec, which not much HW will support yet - see commit 2c255223362e. In theory we don't need that for the fixed, non-IMPDEF events, but I did not complicate perf tool with that mixed support. That's the reason for which I paused smmuv3-pmcg.json upstream in [3]. I will revive that for new gen HW when concrete IMPDEF events known and shared. Thanks, John > > Thanks for your help! > > Leo > > [1] https://lore.kernel.org/lkml/1607080216-36968-1-git-send-email-john.garry@huawei.com/ > [2] pmu-events/arch/arm64/freescale/imx8mm/sys/ddrc.json > [3] https://lore.kernel.org/lkml/1604666153-4187-6-git-send-email-john.garry@huawei.com/ > . >