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;
Date:   Tue, 9 Nov 2021 09:48:43 +0800
From:   Leo Yan <leo.yan@linaro.org>
To:     John Garry <john.garry@huawei.com>
Cc:     linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>
Subject: Re: Question: SMMUv3 PMU event aliasing
Message-ID: <20211109014843.GD1388819@leoy-ThinkPad-X240s>
References: <20211108121941.GC1267967@leoy-ThinkPad-X240s>
 <8b24f36b-6459-c13c-bf19-b9f588eb6b8e@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8b24f36b-6459-c13c-bf19-b9f588eb6b8e@huawei.com>
Precedence: bulk

Hi John,

On Mon, Nov 08, 2021 at 12:41:33PM +0000, John Garry wrote:

[...]

> > 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 for info.  When send out the new patch, you are welcome to Cc
to me, I am glad to give a test on D06 board (its IIDR is zero, so
I need to tweak a bit in driver for IIDR :)).

Thanks,
Leo