Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yuchao Zhang" <ndaugoing@gmail.com>
Cc: kvmarm@lists.linux.dev, "Oliver Upton" <oupton@kernel.org>,
	"Marc Zyngier" <maz@kernel.org>
Subject: Re: [PATCH v2] KVM: selftests: arm64: Add test for cross-vCPU LPI disable race
Date: Tue, 22 Sep 2026 11:03:26 +0000	[thread overview]
Message-ID: <20260922110326.AA0491F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922105331.40498-1-ndaugoing@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] selftests: kvm: missing mandatory kvm_arch_has_default_irqchip() check
--

commit 41b2f5071c9e0e643d02d3f1806d75461776914a
Author: Yuchao Zhang <ndaugoing@gmail.com>

KVM: selftests: arm64: Add test for cross-vCPU LPI disable race

This patch adds a selftest to validate the behavior of remote LPI disabling
while the target vCPU has in-flight or overflowing LPIs. It configures an
ITS with multiple LPIs targeting vCPU 0, forcing its List Registers to
overflow, while vCPU 1 repeatedly toggles GICR_CTLR.EnableLPIs on vCPU 0's
redistributor.

> diff --git a/tools/testing/selftests/kvm/arm64/vgic_lpi_disable.c b/tools/testing/selftests/kvm/arm64/vgic_lpi_disable.c
> new file mode 100644
> index 0000000000000..d3480369d7607
> --- /dev/null
> +++ b/tools/testing/selftests/kvm/arm64/vgic_lpi_disable.c
[ ... ]
> +int main(int argc, char **argv)
> +{
> +	int opt;
> +
> +	TEST_REQUIRE(kvm_supports_vgic_v3());

[Severity: Medium]
Should this code also include a check for kvm_arch_has_default_irqchip()?

The KVM subsystem guidelines mandate that any selftest requiring an in-kernel
IRQ chip must call TEST_REQUIRE(kvm_arch_has_default_irqchip()). This ensures
the test is correctly skipped on platforms without default IRQ chip support.

> +
> +	while ((opt = getopt(argc, argv, "i:e:h")) != -1) {
> +		switch (opt) {

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260922105331.40498-1-ndaugoing@gmail.com?part=1

  reply	other threads:[~2026-09-22 11:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18  4:02 [PATCH v2 0/1] KVM: arm64: vgic: fix UAF/crash on remote LPI disable zjamg
2026-09-18  4:02 ` [PATCH v2] KVM: arm64: vgic: Do not remove in-flight LPIs from AP list on disable zjamg
2026-09-18  7:22   ` Fuad Tabba
2026-09-18 11:50     ` Yuchao Zhang
2026-09-18 11:58       ` Fuad Tabba
2026-09-18 19:15         ` Oliver Upton
2026-09-20 23:54           ` Marc Zyngier
2026-09-20  1:49 ` [PATCH v3 0/1] KVM: arm64: vgic: Drop last_lr_irq and serialize overflow EOI replay Yuchao Zhang
2026-09-20  1:49   ` [PATCH v3] " Yuchao Zhang
2026-09-20 23:47   ` [PATCH v3 0/1] " Marc Zyngier
2026-09-22 10:16     ` Yuchao Zhang
2026-09-22 10:16     ` [PATCH] KVM: selftests: arm64: Add test for cross-vCPU LPI disable race Yuchao Zhang
2026-09-22 10:29       ` sashiko-bot
2026-09-22 10:53         ` Yuchao Zhang
2026-09-22 10:53         ` [PATCH v2] " Yuchao Zhang
2026-09-22 11:03           ` sashiko-bot [this message]
2026-09-22 11:24             ` Yuchao Zhang
2026-09-22 17:08           ` Fuad Tabba
2026-09-22 17:05     ` [PATCH v3 0/1] KVM: arm64: vgic: Drop last_lr_irq and serialize overflow EOI replay Fuad Tabba

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=20260922110326.AA0491F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=ndaugoing@gmail.com \
    --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