From: Rob Herring <robh@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Eric Auger <eric.auger@redhat.com>,
kvmarm@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9
Date: Thu, 2 Jan 2025 10:04:02 -0600 [thread overview]
Message-ID: <20250102160402.GB3990035-robh@kernel.org> (raw)
In-Reply-To: <20241220072240.1003352-1-anshuman.khandual@arm.com>
On Fri, Dec 20, 2024 at 12:52:33PM +0530, Anshuman Khandual wrote:
> This series adds fine grained trap control in EL2 required for FEAT_PMUv3p9
> registers like PMICNTR_EL0, PMICFILTR_EL0, and PMUACR_EL1 which are already
> being used in the kernel. This is required to prevent their EL1 access trap
> into EL2.
>
> PMZR_EL0 register trap control i.e HDFGWTR2_EL2.nPMZR_EL0 remains unchanged
> for now as it does not get accessed in the kernel, and there is no plan for
> its access from user space.
>
> I have taken the liberty to pick up all the review tags for patches related
> to tools sysreg update from the KVM FGT2 V2 patch series posted earlier.
>
> https://lore.kernel.org/all/20241210055311.780688-1-anshuman.khandual@arm.com/
>
> Rob had earler mentioned about FEAT_FGT2 based trap control requirement for
> FEAT_PMUv3p9 registers that are currently being used in kernel. The context
> can be found here.
>
> https://lore.kernel.org/all/20241216234251.GA629562-robh@kernel.org/
>
> This series is based on v6.13-rc3
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Ryan Roberts <ryan.roberts@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Mark Brown <robh@kernel.org>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Oliver Upton <oliver.upton@linux.dev>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Eric Auger <eric.auger@redhat.com>
> Cc: kvmarm@lists.linux.dev
> Cc: linux-doc@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
>
> Anshuman Khandual (7):
> arm64/sysreg: Update register fields for ID_AA64MMFR0_EL1
> arm64/sysreg: Add register fields for HDFGRTR2_EL2
> arm64/sysreg: Add register fields for HDFGWTR2_EL2
> arm64/sysreg: Add register fields for HFGITR2_EL2
> arm64/sysreg: Add register fields for HFGRTR2_EL2
> arm64/sysreg: Add register fields for HFGWTR2_EL2
> arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9
In case it is not clear, this series should be applied to 6.13 as the 2
PMUv3p9 features already landed in 6.13 (per counter EL0 control) and
6.12 (ICNTR).
Rob
next prev parent reply other threads:[~2025-01-02 16:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 7:22 [PATCH 0/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9 Anshuman Khandual
2024-12-20 7:22 ` [PATCH 1/7] arm64/sysreg: Update register fields for ID_AA64MMFR0_EL1 Anshuman Khandual
2024-12-20 7:22 ` [PATCH 2/7] arm64/sysreg: Add register fields for HDFGRTR2_EL2 Anshuman Khandual
2024-12-20 7:22 ` [PATCH 3/7] arm64/sysreg: Add register fields for HDFGWTR2_EL2 Anshuman Khandual
2024-12-20 7:22 ` [PATCH 4/7] arm64/sysreg: Add register fields for HFGITR2_EL2 Anshuman Khandual
2024-12-20 7:22 ` [PATCH 5/7] arm64/sysreg: Add register fields for HFGRTR2_EL2 Anshuman Khandual
2024-12-20 7:22 ` [PATCH 6/7] arm64/sysreg: Add register fields for HFGWTR2_EL2 Anshuman Khandual
2024-12-20 7:22 ` [PATCH 7/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9 Anshuman Khandual
2025-01-02 15:57 ` Rob Herring
2025-01-02 16:04 ` Rob Herring [this message]
2025-01-07 12:13 ` [PATCH 0/7] " Catalin Marinas
2025-01-07 13:42 ` Marc Zyngier
2025-01-07 22:13 ` Rob Herring
2025-01-08 11:15 ` Marc Zyngier
2025-01-08 13:47 ` Rob Herring
2025-01-08 14:02 ` Marc Zyngier
2025-01-16 15:32 ` Catalin Marinas
2025-01-17 22:07 ` Rob Herring
2025-01-28 9:11 ` Anshuman Khandual
2025-01-29 18:03 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250102160402.GB3990035-robh@kernel.org \
--to=robh@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=eric.auger@redhat.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).