The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
	robh@kernel.org
Cc: Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Marc Zyngier <maz@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	kvmarm@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH V3] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9
Date: Tue, 29 Apr 2025 11:07:28 +0530	[thread overview]
Message-ID: <06140631-c3cb-4837-bb4c-bdff30863ad2@arm.com> (raw)
In-Reply-To: <ddeb3df1-995b-44f4-ad20-50edfb906a28@arm.com>



On 3/12/25 09:16, Anshuman Khandual wrote:
> 
> 
> On 3/11/25 22:47, Catalin Marinas wrote:
>> On Thu, 27 Feb 2025 09:21:19 +0530, Anshuman Khandual wrote:
>>> FEAT_PMUv3p9 registers such as PMICNTR_EL0, PMICFILTR_EL0, and PMUACR_EL1
>>> access from EL1 requires appropriate EL2 fine grained trap configuration
>>> via FEAT_FGT2 based trap control registers HDFGRTR2_EL2 and HDFGWTR2_EL2.
>>> Otherwise such register accesses will result in traps into EL2.
>>>
>>> Add a new helper __init_el2_fgt2() which initializes FEAT_FGT2 based fine
>>> grained trap control registers HDFGRTR2_EL2 and HDFGWTR2_EL2 (setting the
>>> bits nPMICNTR_EL0, nPMICFILTR_EL0 and nPMUACR_EL1) to enable access into
>>> PMICNTR_EL0, PMICFILTR_EL0, and PMUACR_EL1 registers.
>>>
>>> [...]
>>
>> Applied to arm64 (for-next/el2-enable-feat-pmuv3p9), thanks!
>>
>> [1/1] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9
>>       https://git.kernel.org/arm64/c/858c7bfcb35e
>>
>> I removed Cc: stable since, if it gets backported automatically, it will
>> miss the sysreg updates and break the build. Please send it to stable
>> directly once it lands upstream, together with the dependencies.
> 
> Sure, will do that.
> 

Just FYI,

This patch along with required tools sysreg patches are merged in applicable
stable branches which are now available in v6.12.25 and v6.14.4 respectively.

      reply	other threads:[~2025-04-29  5:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27  3:51 [PATCH V3] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9 Anshuman Khandual
2025-03-11 17:17 ` Catalin Marinas
2025-03-12  3:46   ` Anshuman Khandual
2025-04-29  5:37     ` Anshuman Khandual [this message]

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=06140631-c3cb-4837-bb4c-bdff30863ad2@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --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=stable@vger.kernel.org \
    --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