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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 25B9BC433EF for ; Mon, 8 Nov 2021 12:43:55 +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 DAA05610F8 for ; Mon, 8 Nov 2021 12:43:54 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org DAA05610F8 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From:CC: 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=vsIsaTvjAahbzo5CoMlc8DRxkFdC3ZZKGJ9qqHDCbMU=; b=nbZyReyWqm4KuYguVddS0NI1+D l8OoI+2cmJ6yHT3WIt15PEcGciOoTNDGqBgTKfRfQDldVSsWG/+MzXIrYaICnzgI8eh0/44oFode+ yG7vvbqrmN+Sr369B28e3gl/BRCTSKQFcve/AtTu9G46jxD4ULI9SJXo43pkTwbdMKVR0p5uJLQDN EIc1zi1KQKkPuJZxefMB1pfARd4aQjXvr2rh3dP7tUJTvZtJV7HaxhZ0XHgGoNjj9+fyPU8FC2je8 Th0mkvRPl3CX5rBr2fwb9AodIJOEyBgs/aDDT5vbed30QZcoD74FlgRPU6tu2MXBbZXX08FSUXyuQ yR+50BEA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mk3yT-00GOsD-GM; Mon, 08 Nov 2021 12:42:09 +0000 Received: from frasgout.his.huawei.com ([185.176.79.56]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mk3yP-00GOqg-HP for linux-arm-kernel@lists.infradead.org; Mon, 08 Nov 2021 12:42:07 +0000 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-Language: en-US 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 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211108_044205_786757_6C2277FF X-CRM114-Status: GOOD ( 19.93 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.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/ > . > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel