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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 6304FC83F1A for ; Thu, 17 Jul 2025 13:12:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=crLW5Vrd54qLw8nj/7RWj8EBP7UgxvD/1amZrbwaJOk=; b=gkgSH4ZaiacHcyuQqhEqzIIogF T8j2fA+Pic6Mtv8BdyTXzOcaOnAMw9LLwyrSChveTTcibwIJjQbzsZIvJUH/7KuO+ReKzLnFjxBLi LGgZsXZN+gOte53bpTRBWDv96S3VTqwHaEl29YP6StZXqRc6rYM59gmWTHH5J3bwi8M7KgWcD3uKI S+du/eVbiD8jXHERY96jyZ3VsjVMTnDFOQXfMYP88OxyEDEa3xEqkd9aDO6FlWyUeUjezxzNOUUjE lRyndo+rKXJbBXgUG5X7SZGD/0QU30n5YrO3XeH0JwZsSunWyYhsR3p4yfplgjrHLaX6OhXwO1NJg QvHL512g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1ucOPG-0000000ADoU-1GXK; Thu, 17 Jul 2025 13:12:14 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1ucNAV-0000000A1er-0ER3 for linux-arm-kernel@lists.infradead.org; Thu, 17 Jul 2025 11:52:55 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id 29126601E0; Thu, 17 Jul 2025 11:52:54 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 276E6C4CEF6; Thu, 17 Jul 2025 11:52:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1752753173; bh=768jnmLVmr/V6ZyVJm0rYYFSz76GLOLtXyYMf0pndCk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=O7UGW1d3rjbTWkmaRHwUuO+4xw8pbVWJb/FnZE7jAYa9Rk8FiEZuhmIoIdcRiu4mP mvKD5TYzhiaeMPUaszLAa+1ep6tyzZSBcGwilCx7XZjbTF0FZ3ZxEbC4SvfYJKkYwc DIDM5QDywPSAo2EGXHsTDJUBRSkSyf8dlB49GC5QeXSpNnH9nObwZU0RWPX5heiSTK NijJp76wqTWn3Ogf7f7IALBu523yGOa1QJlgPBzKU/WbmKrDX3x8l32U7JtoH+889G BV3VLFNA0U1UeQXSHf7wGX5P44vMv6wJYnnZNe0fJO/lbdi//0Sh3GKTSbm00oul2K knMskkyRTSktw== Date: Thu, 17 Jul 2025 12:52:46 +0100 From: Will Deacon To: James Clark Cc: Catalin Marinas , Mark Rutland , Jonathan Corbet , Marc Zyngier , Oliver Upton , Joey Gouly , Suzuki K Poulose , Zenghui Yu , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Namhyung Kim , Alexander Shishkin , Jiri Olsa , Ian Rogers , Adrian Hunter , leo.yan@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, linux-doc@vger.kernel.org, kvmarm@lists.linux.dev Subject: Re: [PATCH v3 04/10] arm64/boot: Enable EL2 requirements for SPE_FEAT_FDS Message-ID: References: <20250605-james-perf-feat_spe_eft-v3-0-71b0c9f98093@linaro.org> <20250605-james-perf-feat_spe_eft-v3-4-71b0c9f98093@linaro.org> <04d52182-6043-4eaf-a898-9f8ccc893e5f@linaro.org> <80b7c29e-83b9-46a4-826e-d252ad425d4d@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <80b7c29e-83b9-46a4-826e-d252ad425d4d@linaro.org> 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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Jul 15, 2025 at 02:28:19PM +0100, James Clark wrote: > > > On 15/07/2025 2:10 pm, James Clark wrote: > > > > > > On 15/07/2025 1:57 pm, Will Deacon wrote: > > > On Tue, Jul 15, 2025 at 01:48:03PM +0100, James Clark wrote: > > > > > > > > > > > > On 14/07/2025 2:54 pm, Will Deacon wrote: > > > > > On Thu, Jun 05, 2025 at 11:49:02AM +0100, James Clark wrote: > > > > > > SPE data source filtering (optional from Armv8.8) > > > > > > requires that traps to > > > > > > the filter register PMSDSFR be disabled. Document the requirements and > > > > > > disable the traps if the feature is present. > > > > > > > > > > > > Tested-by: Leo Yan > > > > > > Signed-off-by: James Clark > > > > > > --- > > > > > >    Documentation/arch/arm64/booting.rst | 11 +++++++++++ > > > > > >    arch/arm64/include/asm/el2_setup.h   | 14 ++++++++++++++ > > > > > >    2 files changed, 25 insertions(+) > > > > > > > > > > > > diff --git a/Documentation/arch/arm64/booting.rst > > > > > > b/Documentation/ arch/arm64/booting.rst > > > > > > index dee7b6de864f..abd75085a239 100644 > > > > > > --- a/Documentation/arch/arm64/booting.rst > > > > > > +++ b/Documentation/arch/arm64/booting.rst > > > > > > @@ -404,6 +404,17 @@ Before jumping into the kernel, the > > > > > > following conditions must be met: > > > > > >        - HDFGWTR2_EL2.nPMICFILTR_EL0 (bit 3) must be > > > > > > initialised to 0b1. > > > > > >        - HDFGWTR2_EL2.nPMUACR_EL1 (bit 4) must be initialised to 0b1. > > > > > > +  For CPUs with SPE data source filtering (FEAT_SPE_FDS): > > > > > > + > > > > > > +  - If EL3 is present: > > > > > > + > > > > > > +    - MDCR_EL3.EnPMS3 (bit 42) must be initialised to 0b1. > > > > > > + > > > > > > +  - If the kernel is entered at EL1 and EL2 is present: > > > > > > + > > > > > > +    - HDFGRTR2_EL2.nPMSDSFR_EL1 (bit 19) must be initialised to 0b1. > > > > > > +    - HDFGWTR2_EL2.nPMSDSFR_EL1 (bit 19) must be initialised to 0b1. > > > > > > + > > > > > >      For CPUs with Memory Copy and Memory Set > > > > > > instructions (FEAT_MOPS): > > > > > >      - If the kernel is entered at EL1 and EL2 is present: > > > > > > diff --git a/arch/arm64/include/asm/el2_setup.h > > > > > > b/arch/arm64/ include/asm/el2_setup.h > > > > > > index 1e7c7475e43f..02b4a7fc016e 100644 > > > > > > --- a/arch/arm64/include/asm/el2_setup.h > > > > > > +++ b/arch/arm64/include/asm/el2_setup.h > > > > > > @@ -279,6 +279,20 @@ > > > > > >        orr    x0, x0, #HDFGRTR2_EL2_nPMICFILTR_EL0 > > > > > >        orr    x0, x0, #HDFGRTR2_EL2_nPMUACR_EL1 > > > > > >    .Lskip_pmuv3p9_\@: > > > > > > +    mrs    x1, id_aa64dfr0_el1 > > > > > > +    ubfx    x1, x1, #ID_AA64DFR0_EL1_PMSVer_SHIFT, #4 > > > > > > +    /* If SPE is implemented, */ > > > > > > +    cmp    x1, #ID_AA64DFR0_EL1_PMSVer_IMP > > > > > > +    b.lt    .Lskip_spefds_\@ > > > > > > +    /* we can read PMSIDR and */ > > > > > > +    mrs_s    x1, SYS_PMSIDR_EL1 > > > > > > +    and    x1, x1,  #PMSIDR_EL1_FDS > > > > > > +    /* if FEAT_SPE_FDS is implemented, */ > > > > > > +    cbz    x1, .Lskip_spefds_\@ > > > > > > +    /* disable traps to PMSDSFR. */ > > > > > > +    orr    x0, x0, #HDFGRTR2_EL2_nPMSDSFR_EL1 > > > > > > > > > > Why is this being done here rather than alongside the existing SPE > > > > > configuration of HDFGRTR_EL2 and HDFGWTR_EL2 near the start of > > > > > __init_el2_fgt? > > > > > > > > > I thought everything was separated by which trap configs it writes to, > > > > rather than the feature. This SPE feature is in HDFGRTR2 so I put it in > > > > __init_el2_fgt2 rather than __init_el2_fgt. > > > > > > That's fair; __init_el2_fgt isn't the right place. But the redundancy of > > > re-reading PMSVer from DFR0 is a little jarring. > > > > > > > I suppose we could have a single __init_el2_spe that writes to > > > > both HDFGRTR > > > > and HDFGRTR2 but we'd have to be careful to not overwrite what > > > > was already > > > > done in the other sections. > > > > > > Right, perhaps it would be clearer to have trap-preserving macros for > > > features in a specific ID register rather than per-trap configuration > > > register macros. > > > > > > In other words, we have something like __init_fgt_aa64dfr0 which would > > > configure the FGT and FGT2 registers based on features in aa64dfr0. I > > > think you'd need to have a play to see how it ends up looking but the > > > main thing to avoid is having duplicate ID register parsing code for > > > setting up FGT and FGT2 traps. > > > > > > > I'll give it a go but that could end up being fragile to something that > > is dependent on two different ID registers in the future. Then we'd end > > up in the same situation for a different reason. > > > > I think I've run into it already. Wouldn't checking for FGT and FGT2 have to > be repeated when doing each ID register? Now we only do that once at the > start of __init_el2_fgt and __init_el2_fgt2, even if we might sometimes > check a different ID register twice. But if we flipped it we'd always have > to repeat those. Bah, this is quite horrible! Maybe the best we can do for now is have a macro for safely getting at PMBIDR? At some point, I suspect this whole FGT-configuration logic will need reworking but at the moment it's hard to see what the best approach would be. Will