All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mark Brown" <broonie@kernel.org>
Cc: "Oliver Upton" <oupton@kernel.org>,
	"Marc Zyngier" <maz@kernel.org>,
	kvmarm@lists.linux.dev
Subject: Re: [PATCH v17 10/14] KVM: selftests: arm64: Add GCS registers to get-reg-list
Date: Fri, 31 Jul 2026 13:03:27 +0000	[thread overview]
Message-ID: <20260731130327.71B6E1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260731-arm64-gcs-v17-10-5e39ca01b14e@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] GCS registers in `el2_regs` are inserted out of order compared to their system register encoding, violating the array's sorting convention.
--

--- Patch [10]: [PATCH v17 10/14] KVM: selftests: arm64: Add GCS registers to get-reg-list ---
commit 54610fb50b06e8daefb5c3cb9a29fbd4f7e9af9a
Author: Mark Brown <broonie@kernel.org>

KVM: selftests: arm64: Add GCS registers to get-reg-list

This commit adds the new Guarded Control Stack (GCS) registers to the
get-reg-list selftest for ARM64. It includes GCSCR_ELx, GCSCRE0_EL1, and
GCSPR_ELx in the validation arrays.

> diff --git a/tools/testing/selftests/kvm/arm64/get-reg-list.c b/tools/testing/selftests/kvm/arm64/get-reg-list.c
> --- a/tools/testing/selftests/kvm/arm64/get-reg-list.c
> +++ b/tools/testing/selftests/kvm/arm64/get-reg-list.c
[ ... ]
> @@ -757,6 +767,8 @@ static __u64 el2_regs[] = {
>  	SYS_REG(PIRE0_EL2),
>  	SYS_REG(PIR_EL2),
>  	SYS_REG(POR_EL2),
> +	SYS_REG(GCSPR_EL2),
> +	SYS_REG(GCSCR_EL2),

[Severity: Low]
This isn't a bug, but are these registers inserted out of order compared to
their system register encoding?

The el2_regs array appears to be sorted by encoding (Op0, Op1, CRn, CRm,
Op2). Both GCSCR_EL2 (3, 4, 2, 5, 0) and GCSPR_EL2 (3, 4, 2, 5, 1) have
CRn=2, which suggests they should be placed earlier in the array, perhaps
near VTCR_EL2 or VNCR_EL2.

Also, should GCSCR_EL2 (Op2=0) precede GCSPR_EL2 (Op2=1) here to maintain
the correct relative ordering?

>  	SYS_REG(AMAIR_EL2),
>  	SYS_REG(VBAR_EL2),
>  	SYS_REG(CONTEXTIDR_EL2),

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260731-arm64-gcs-v17-0-5e39ca01b14e@kernel.org?part=10

  reply	other threads:[~2026-07-31 13:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 12:25 [PATCH v17 00/14] KVM: arm64: Provide guest support for GCS Mark Brown
2026-07-31 12:25 ` [PATCH v17 01/14] arm64/gcs: Ensure FGTs for EL1 GCS instructions are disabled Mark Brown
2026-07-31 12:25 ` [PATCH v17 02/14] KVM: arm64: Fix FGT mapping for HFGITR_EL2.nGCSEPP Mark Brown
2026-07-31 13:03   ` sashiko-bot
2026-07-31 13:47     ` Mark Brown
2026-07-31 12:25 ` [PATCH v17 03/14] KVM: arm64: Manage GCS access and registers for guests Mark Brown
2026-07-31 12:56   ` sashiko-bot
2026-07-31 15:26     ` Mark Brown
2026-07-31 12:25 ` [PATCH v17 04/14] KVM: arm64: Ensure GCS memory effects are visible Mark Brown
2026-07-31 12:25 ` [PATCH v17 05/14] KVM: arm64: Set PSTATE.EXLOCK when entering an exception Mark Brown
2026-07-31 12:25 ` [PATCH v17 06/14] KVM: arm64: Validate GCS exception lock when emulating ERET Mark Brown
2026-07-31 12:25 ` [PATCH v17 07/14] KVM: arm64: Forward GCS exceptions to nested guests Mark Brown
2026-07-31 12:58   ` sashiko-bot
2026-07-31 12:25 ` [PATCH v17 08/14] KVM: arm64: Enforce EXLOCK for SPSR and ELR Mark Brown
2026-07-31 12:25 ` [PATCH v17 09/14] KVM: arm64: Allow GCS to be enabled for guests Mark Brown
2026-07-31 12:25 ` [PATCH v17 10/14] KVM: selftests: arm64: Add GCS registers to get-reg-list Mark Brown
2026-07-31 13:03   ` sashiko-bot [this message]
2026-07-31 13:31     ` Mark Brown
2026-07-31 12:25 ` [PATCH v17 11/14] KVM: selftests: arm64: Add GCS to set_id_regs Mark Brown
2026-07-31 12:25 ` [PATCH v17 12/14] KVM: selftests: arm64: Only restore SPSR_EL1 and ELR_EL1 if they change Mark Brown
2026-07-31 12:25 ` [PATCH v17 13/14] tools: Synchronise the kernel esr.h Mark Brown
2026-07-31 12:25 ` [PATCH v17 14/14] KVM: selftests: arm64: Add GCS EXLOCK exception emulation test Mark Brown

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=20260731130327.71B6E1F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=broonie@kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=maz@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.