From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org,
Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Mark Rutland <mark.rutland@arm.com>, Mark Brown <robh@kernel.org>,
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: (subset) [PATCH V2 0/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9
Date: Tue, 18 Feb 2025 19:06:33 +0000 [thread overview]
Message-ID: <Z7TaOUcjP0kME5ly@arm.com> (raw)
In-Reply-To: <173990541533.375660.5963781767181928314.b4-ty@arm.com>
On Tue, Feb 18, 2025 at 07:03:49PM +0000, Catalin Marinas wrote:
> On Mon, 03 Feb 2025 10:38:21 +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.
> >
> > [...]
>
> Applied to arm64 (for-next/el2-enable-feat-pmuv3p9), thanks!
>
> [7/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9
> https://git.kernel.org/arm64/c/f134bbc054ae
"b4 ty" ignored the other patches. I applied the sysreg ones to the
arm64 for-next/sysreg branch in case they need to get pulled into other
trees (e.g. KVM). The above patch is on top of the other sysreg patches.
--
Catalin
next prev parent reply other threads:[~2025-02-18 19:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 5:08 [PATCH V2 0/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9 Anshuman Khandual
2025-02-03 5:08 ` [PATCH V2 1/7] arm64/sysreg: Update register fields for ID_AA64MMFR0_EL1 Anshuman Khandual
2025-02-03 5:08 ` [PATCH V2 2/7] arm64/sysreg: Add register fields for HDFGRTR2_EL2 Anshuman Khandual
2025-02-03 5:08 ` [PATCH V2 3/7] arm64/sysreg: Add register fields for HDFGWTR2_EL2 Anshuman Khandual
2025-02-03 5:08 ` [PATCH V2 4/7] arm64/sysreg: Add register fields for HFGITR2_EL2 Anshuman Khandual
2025-02-03 5:08 ` [PATCH V2 5/7] arm64/sysreg: Add register fields for HFGRTR2_EL2 Anshuman Khandual
2025-02-03 5:08 ` [PATCH V2 6/7] arm64/sysreg: Add register fields for HFGWTR2_EL2 Anshuman Khandual
2025-02-03 5:08 ` [PATCH V2 7/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9 Anshuman Khandual
2025-02-24 14:11 ` Mark Rutland
2025-02-25 6:17 ` Anshuman Khandual
2025-02-26 17:14 ` Rob Herring
2025-02-26 17:44 ` Catalin Marinas
2025-02-17 5:42 ` [PATCH V2 0/7] " Anshuman Khandual
2025-02-18 19:03 ` (subset) " Catalin Marinas
2025-02-18 19:06 ` Catalin Marinas [this message]
2025-03-01 7:58 ` Will Deacon
2025-03-01 11:11 ` 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=Z7TaOUcjP0kME5ly@arm.com \
--to=catalin.marinas@arm.com \
--cc=anshuman.khandual@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=robh@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.