Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: "Oliver Upton" <oupton@kernel.org>,
	kvm@vger.kernel.org, kvmarm@lists.linux.dev
Subject: Re: [PATCH v2 26/28] KVM: arm64: Add FEAT_NV3 detection
Date: Tue, 14 Jul 2026 15:42:33 +0100	[thread overview]
Message-ID: <86mrvtoco6.wl-maz@kernel.org> (raw)
In-Reply-To: <20260714100704.206731F000E9@smtp.kernel.org>

On Tue, 14 Jul 2026 11:07:03 +0100,
sashiko-bot@kernel.org wrote:
> 
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> 
> Pre-existing issues:
> - [High] Writes to control-plane system registers (SYS_NVHCR_EL2 and SYS_VNCR_EL2) are missing the architecturally required `isb()` synchronization barrier.
> --
> 
> --- Patch [26]: [PATCH v2 26/28] KVM: arm64: Add FEAT_NV3 detection ---
> commit 1e08d22547f3313a77b075620f905436357c4b40
> Author: Marc Zyngier <maz@kernel.org>
> 
> KVM: arm64: Add FEAT_NV3 detection
>     
> Now that everything is in place to engage the FEAT_NV3 fast-path,
> add the detection code to cpufeature.c.
> 
> > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> > index c9c124b0ccc8e..6ae1c816e2010 100644
> > --- a/arch/arm64/kernel/cpufeature.c
> > +++ b/arch/arm64/kernel/cpufeature.c
> > @@ -2627,6 +2627,13 @@ static const struct arm64_cpu_capabilities arm64_features[] = {
> >  		.matches = has_cpuid_feature,
> >  		ARM64_CPUID_FIELDS(ID_AA64MMFR4_EL1, NV_frac, NV2P1)
> >  	},
> > +	{
> > +		.desc = "FEAT_NV3",
> > +		.capability = ARM64_HAS_NV3,
> > +		.type = ARM64_CPUCAP_SYSTEM_FEATURE,
> > +		.matches = has_cpuid_feature,
> > +		ARM64_CPUID_FIELDS(ID_AA64MMFR4_EL1, NV_frac, NV3)
> > +	},
> 
> [Severity: High]
> This isn't a bug introduced by this patch, but enabling FEAT_NV3 here exposes
> pre-existing paths where control-plane system registers are written without
> the architecturally required immediate isb() synchronization barrier.

Plonk.

	M.

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

  reply	other threads:[~2026-07-14 14:42 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  9:16 [PATCH v2 00/28] KVM: arm64: Add support for FEAT_NV2p1 and FEAT_NV3 Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 01/28] arm64: sysreg: Emit RESx/UNKN values for Mapping/Fields definitions Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 02/28] arm64: Update ID_AA64MMFR4_EL1 description to 2026-03 JSON release Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 03/28] KVM: arm64: Merge guest's HCRX_EL2 using NV_HCRX_GUEST_EXCLUDE Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 04/28] KVM: arm64: Drop __HCRX_EL2_* masks Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 05/28] KVM: arm64: Plumb HCRX_EL2.SRMASKEn in HCRX_EL2 sanitisation Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 06/28] KVM: arm64: Classify CPTR_EL2 as a SR_LOC_SPECIAL register Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 07/28] KVM: arm64: Don't evaluate HCR_EL2.NV nor HFGITR_EL2.ERET on ERET fast path Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 08/28] arm64: Add ARM64_HAS_NV2P1 capability Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 09/28] KVM: arm64: Relax CPTR_EL2 handling when FEAT_NV2p1 is present Marc Zyngier
2026-07-14 10:12   ` sashiko-bot
2026-07-14 14:12     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 10/28] KVM: arm64: Relax CNTHCTL_EL2 " Marc Zyngier
2026-07-14  9:53   ` sashiko-bot
2026-07-14 14:22     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 11/28] KVM: arm64: Expose FEAT_NV2p1 to NV guests Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 12/28] arm64: Add FEAT_NV2p1 detection Marc Zyngier
2026-07-14  9:46   ` sashiko-bot
2026-07-14 11:45     ` Marc Zyngier
2026-07-14 13:18       ` Fuad Tabba
2026-07-14  9:16 ` [PATCH v2 13/28] arm64: sysreg: Add NVHCR_EL2 description as a mirror of HCR_EL2 Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 14/28] arm64: sysreg: Add HCRX_EL2 bits related to FEAT_NV3 Marc Zyngier
2026-07-14  9:45   ` sashiko-bot
2026-07-14 13:04     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 15/28] arm64: Add ARM64_HAS_NV3 capability Marc Zyngier
2026-07-14  9:40   ` sashiko-bot
2026-07-14 11:42     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 16/28] KVM: arm64: Split NV-specific exit fixups from the non-NV handling Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 17/28] KVM: arm64: Add NV3 control bits to HCRX_EL2 sanitisation Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 18/28] KVM: arm64: Add kvm_has_nv{2,3}() predicates Marc Zyngier
2026-07-14  9:48   ` sashiko-bot
2026-07-14 14:23     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 19/28] KVM: arm64: Make HCR_EL2 a non-VNCR register Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 20/28] KVM: arm64: Add sanitisation for NVHCR_EL2 Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 21/28] KVM: arm64: Add NVHCR_EL2 handling to the sysreg array Marc Zyngier
2026-07-14 10:24   ` sashiko-bot
2026-07-14 12:56     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 22/28] KVM: arm64: Add routing for NVHCR_EL2 trap Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 23/28] KVM: arm64: Add NVHCR_EL2 context switching Marc Zyngier
2026-07-14 10:03   ` sashiko-bot
2026-07-14 14:44     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 24/28] KVM: arm64: Engage NV3 ERET trap elision Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 25/28] KVM: arm64: Engage NV3 TLBI " Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 26/28] KVM: arm64: Add FEAT_NV3 detection Marc Zyngier
2026-07-14 10:07   ` sashiko-bot
2026-07-14 14:42     ` Marc Zyngier [this message]
2026-07-14  9:16 ` [PATCH v2 27/28] KVM: arm64: Expose FEAT_NV3 to guests Marc Zyngier
2026-07-14 10:15   ` sashiko-bot
2026-07-14 14:41     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 28/28] arm64: Add override for ID_AA64MMFR4_EL1.NV_frac Marc Zyngier

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=86mrvtoco6.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=oupton@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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