linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Oliver Upton <oliver.upton@linux.dev>,
	Joey Gouly <joey.gouly@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Shuah Khan <shuah@kernel.org>, Mark Brown <broonie@kernel.org>,
	kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	kvmarm@lists.linux.dev, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v4 0/9] arm64: Support 2024 dpISA extensions
Date: Tue, 07 Jan 2025 17:18:43 +0000	[thread overview]
Message-ID: <86zfk2wnik.wl-maz@kernel.org> (raw)
In-Reply-To: <173626298431.2741856.11908646584681839796.b4-ty@kernel.org>

On Tue, 07 Jan 2025 16:42:38 +0000,
Will Deacon <will@kernel.org> wrote:
> 
> On Wed, 11 Dec 2024 01:02:45 +0000, Mark Brown wrote:
> > The 2024 architecture release includes a number of data processing
> > extensions, mostly SVE and SME additions with a few others.  These are
> > all very straightforward extensions which add instructions but no
> > architectural state so only need hwcaps and exposing of the ID registers
> > to KVM guests and userspace.
> > 
> > 
> > [...]
> 
> For the sysreg definitions that Marc's fantastic script is happy with,
> applied to arm64 (for-next/cpufeature), thanks!
> 
> [1/9] arm64/sysreg: Update ID_AA64PFR2_EL1 to DDI0601 2024-09
>       https://git.kernel.org/arm64/c/1ad9a56442a0
> [2/9] arm64/sysreg: Update ID_AA64ISAR3_EL1 to DDI0601 2024-09
>       https://git.kernel.org/arm64/c/054339beae58
> [3/9] arm64/sysreg: Update ID_AA64FPFR0_EL1 to DDI0601 2024-09
>       https://git.kernel.org/arm64/c/12b5ff517a19
> [4/9] arm64/sysreg: Update ID_AA64ZFR0_EL1 to DDI0601 2024-09
>       https://git.kernel.org/arm64/c/9a43ee864349
> 
> [6/9] arm64/sysreg: Update ID_AA64ISAR2_EL1 to DDI0601 2024-09
>       https://git.kernel.org/arm64/c/d66e21d59ed0
> 
> The KVM patch needs an Ack from the maintainers and the hwcap change
> probably needs checking in light of [1].

I've now acked the KVM patch in case you want to take it, or I can add
it to the KVM queue, since I already have a merge of the cpufeature
branch.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.


      reply	other threads:[~2025-01-07 17:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  1:02 [PATCH v4 0/9] arm64: Support 2024 dpISA extensions Mark Brown
2024-12-11  1:02 ` [PATCH v4 1/9] arm64/sysreg: Update ID_AA64PFR2_EL1 to DDI0601 2024-09 Mark Brown
2024-12-11  1:02 ` [PATCH v4 2/9] arm64/sysreg: Update ID_AA64ISAR3_EL1 " Mark Brown
2024-12-11  1:02 ` [PATCH v4 3/9] arm64/sysreg: Update ID_AA64FPFR0_EL1 " Mark Brown
2024-12-11  1:02 ` [PATCH v4 4/9] arm64/sysreg: Update ID_AA64ZFR0_EL1 " Mark Brown
2024-12-11  1:02 ` [PATCH v4 5/9] arm64/sysreg: Update ID_AA64SMFR0_EL1 " Mark Brown
2025-01-07 15:13   ` Will Deacon
2025-01-07 15:26     ` Mark Brown
2025-01-07 15:39       ` Will Deacon
2024-12-11  1:02 ` [PATCH v4 6/9] arm64/sysreg: Update ID_AA64ISAR2_EL1 " Mark Brown
2024-12-11  1:02 ` [PATCH v4 7/9] arm64/hwcap: Describe 2024 dpISA extensions to userspace Mark Brown
2024-12-11  1:02 ` [PATCH v4 8/9] KVM: arm64: Allow control of dpISA extensions in ID_AA64ISAR3_EL1 Mark Brown
2025-01-07 17:16   ` Marc Zyngier
2024-12-11  1:02 ` [PATCH v4 9/9] kselftest/arm64: Add 2024 dpISA extensions to hwcap test Mark Brown
2025-01-07 16:42 ` [PATCH v4 0/9] arm64: Support 2024 dpISA extensions Will Deacon
2025-01-07 17:18   ` Marc Zyngier [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=86zfk2wnik.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=joey.gouly@arm.com \
    --cc=kernel-team@android.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=linux-kselftest@vger.kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=shuah@kernel.org \
    --cc=suzuki.poulose@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).