From: Marc Zyngier <maz@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: kvmarm@lists.linux.dev, "Oliver Upton" <oupton@kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH v3 25/28] KVM: arm64: Engage NV3 TLBI trap elision
Date: Wed, 22 Jul 2026 10:04:39 +0100 [thread overview]
Message-ID: <86ldb3e6oo.wl-maz@kernel.org> (raw)
In-Reply-To: <20260722085745.911F01F000E9@smtp.kernel.org>
On Wed, 22 Jul 2026 09:57:45 +0100,
sashiko-bot@kernel.org wrote:
>
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] Stray double semicolon creates an empty statement.
> --
>
> --- Patch [25]: [PATCH v3 25/28] KVM: arm64: Engage NV3 TLBI trap elision ---
> commit dabbb189ece66c0128f9610303e005d9bdd94252
> Author: Marc Zyngier <maz@kernel.org>
>
> KVM: arm64: Engage NV3 TLBI trap elision
>
> This commit enables NV3 TLBI trap elision for guests that are not NV2 aware,
> relaxing the TLBI traps when only the guest's S1 translation is affected.
>
> > diff --git a/arch/arm64/include/asm/kvm_emulate.h b/arch/arm64/include/asm/kvm_emulate.h
> > --- a/arch/arm64/include/asm/kvm_emulate.h
> > +++ b/arch/arm64/include/asm/kvm_emulate.h
> [ ... ]
> > @@ -715,6 +715,19 @@ static inline void vcpu_set_hcrx(struct kvm_vcpu *vcpu)
> [ ... ]
> > + if (!kvm_has_nv2(vcpu->kvm)) {
> > + vcpu->arch.hcrx_el2 |= (HCRX_EL2_NVnTTLB |
> > + HCRX_EL2_NVnTTLBIS);
> > +
> > + if (kvm_has_feat(kvm, ID_AA64ISAR0_EL1, TLB, OS))
> > + vcpu->arch.hcrx_el2 |= HCRX_EL2_NVnTTLBOS;;
>
> [Severity: Low]
> This isn't a bug, but there's a stray double semicolon at the end of this
> statement.
I'll fix that.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-07-22 9:04 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 7:42 [PATCH v3 00/28] KVM: arm64: Add support for FEAT_NV2p1 and FEAT_NV3 Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 01/28] arm64: sysreg: Emit RESx/UNKN values for Mapping/Fields definitions Marc Zyngier
2026-07-22 7:55 ` sashiko-bot
2026-07-22 9:05 ` Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 02/28] arm64: Update ID_AA64MMFR4_EL1 description to 2026-03 JSON release Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 03/28] KVM: arm64: Merge guest's HCRX_EL2 using NV_HCRX_GUEST_EXCLUDE Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 04/28] KVM: arm64: Drop __HCRX_EL2_* masks Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 05/28] KVM: arm64: Plumb HCRX_EL2.SRMASKEn in HCRX_EL2 sanitisation Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 06/28] KVM: arm64: Classify CPTR_EL2 as a SR_LOC_SPECIAL register Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 07/28] KVM: arm64: Don't evaluate HCR_EL2.NV nor HFGITR_EL2.ERET on ERET fast path Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 08/28] arm64: Add ARM64_HAS_NV2P1 capability Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 09/28] KVM: arm64: Relax CPTR_EL2 handling when FEAT_NV2p1 is present Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 10/28] KVM: arm64: Relax CNTHCTL_EL2 " Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 11/28] KVM: arm64: Expose FEAT_NV2p1 to NV guests Marc Zyngier
2026-07-22 8:32 ` sashiko-bot
2026-07-22 9:01 ` Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 12/28] arm64: Add FEAT_NV2p1 detection Marc Zyngier
2026-07-22 8:13 ` sashiko-bot
2026-07-22 8:57 ` Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 13/28] arm64: sysreg: Add NVHCR_EL2 description as a mirror of HCR_EL2 Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 14/28] arm64: sysreg: Add HCRX_EL2 bits related to FEAT_NV3 Marc Zyngier
2026-07-22 8:11 ` sashiko-bot
2026-07-22 8:56 ` Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 15/28] arm64: Add ARM64_HAS_NV3 capability Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 16/28] KVM: arm64: Split NV-specific exit fixups from the non-NV handling Marc Zyngier
2026-07-22 8:23 ` sashiko-bot
2026-07-22 9:08 ` Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 17/28] KVM: arm64: Add NV3 control bits to HCRX_EL2 sanitisation Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 18/28] KVM: arm64: Add kvm_has_nv{2,3}() predicates Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 19/28] KVM: arm64: Make HCR_EL2 a non-VNCR register Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 20/28] KVM: arm64: Add sanitisation for NVHCR_EL2 Marc Zyngier
2026-07-22 8:38 ` sashiko-bot
2026-07-22 9:11 ` Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 21/28] KVM: arm64: Add NVHCR_EL2 handling to the sysreg array Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 22/28] KVM: arm64: Add routing for NVHCR_EL2 trap Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 23/28] KVM: arm64: Add NVHCR_EL2 context switching Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 24/28] KVM: arm64: Engage NV3 ERET trap elision Marc Zyngier
2026-07-22 8:50 ` sashiko-bot
2026-07-22 9:16 ` Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 25/28] KVM: arm64: Engage NV3 TLBI " Marc Zyngier
2026-07-22 8:57 ` sashiko-bot
2026-07-22 9:04 ` Marc Zyngier [this message]
2026-07-22 7:42 ` [PATCH v3 26/28] KVM: arm64: Add FEAT_NV3 detection Marc Zyngier
2026-07-22 8:53 ` sashiko-bot
2026-07-22 9:04 ` Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 27/28] KVM: arm64: Expose FEAT_NV3 to guests Marc Zyngier
2026-07-22 9:06 ` sashiko-bot
2026-07-22 9:18 ` Marc Zyngier
2026-07-22 7:42 ` [PATCH v3 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=86ldb3e6oo.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