stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, will@kernel.org, robh@kernel.org,
	mark.rutland@arm.com
Subject: Re: [PATCH 6.13.y 0/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9
Date: Tue, 8 Apr 2025 17:27:24 +0100	[thread overview]
Message-ID: <Z_VObETYYOHdym9N@arm.com> (raw)
In-Reply-To: <d3a5589f-a231-4d60-9d70-5e0f01dff125@arm.com>

On Tue, Apr 08, 2025 at 03:34:51PM +0530, Anshuman Khandual wrote:
> On 4/8/25 15:23, Greg KH wrote:
> > On Tue, Apr 08, 2025 at 03:08:52PM +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.
> >>
> >> The following commits that enabled access into FEAT_PMUv3p9 registers have
> >> already been merged upstream from 6.13 onwards.
> >>
> >> d8226d8cfbaf ("perf: arm_pmuv3: Add support for Armv9.4 PMU instruction counter")
> >> 0bbff9ed8165 ("perf/arm_pmuv3: Add PMUv3.9 per counter EL0 access control")
> >>
> >> The sysreg patches in this series are required for the final patch which
> >> fixes the actual problem.
> > 
> > But you aren't going to fix the 6.14.y tree?  We can't take patches that
> > skip newer stable releases for obvious reasons.
> > 
> > And 6.13.y is only going to be alive for a few more days, is there some
> > specific reason this is needed now for 6.13.y?
> 
> I have also sent same series for 6.14 stable version as well. It will be
> great to have these patches applied both on 6.13 as well 6.14. Thank you.

TBH, 6.13 is end of life soon, so not sure it's worth carrying those
patches. Do you have a reason for this Anshuman?

-- 
Catalin

  reply	other threads:[~2025-04-08 16:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  9:38 [PATCH 6.13.y 0/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9 Anshuman Khandual
2025-04-08  9:38 ` [PATCH 6.13.y 1/7] arm64/sysreg: Update register fields for ID_AA64MMFR0_EL1 Anshuman Khandual
2025-04-10 15:54   ` Sasha Levin
2025-04-08  9:38 ` [PATCH 6.13.y 2/7] arm64/sysreg: Add register fields for HDFGRTR2_EL2 Anshuman Khandual
2025-04-10 15:56   ` Sasha Levin
2025-04-08  9:38 ` [PATCH 6.13.y 3/7] arm64/sysreg: Add register fields for HDFGWTR2_EL2 Anshuman Khandual
2025-04-10 15:53   ` Sasha Levin
2025-04-08  9:38 ` [PATCH 6.13.y 4/7] arm64/sysreg: Add register fields for HFGITR2_EL2 Anshuman Khandual
2025-04-10 15:54   ` Sasha Levin
2025-04-08  9:38 ` [PATCH 6.13.y 5/7] arm64/sysreg: Add register fields for HFGRTR2_EL2 Anshuman Khandual
2025-04-10 15:53   ` Sasha Levin
2025-04-08  9:38 ` [PATCH 6.13.y 6/7] arm64/sysreg: Add register fields for HFGWTR2_EL2 Anshuman Khandual
2025-04-10 15:55   ` Sasha Levin
2025-04-08  9:38 ` [PATCH 6.13.y 7/7] arm64/boot: Enable EL2 requirements for FEAT_PMUv3p9 Anshuman Khandual
2025-04-10 15:53   ` Sasha Levin
2025-04-08  9:53 ` [PATCH 6.13.y 0/7] " Greg KH
2025-04-08 10:04   ` Anshuman Khandual
2025-04-08 16:27     ` Catalin Marinas [this message]
2025-04-09  2:55       ` Anshuman Khandual
2025-04-08 17:40 ` Rob Herring
2025-04-09  3:36   ` Anshuman Khandual

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=Z_VObETYYOHdym9N@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=anshuman.khandual@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=mark.rutland@arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).