From: sashiko-bot@kernel.org
To: "Fuad Tabba" <fuad.tabba@linux.dev>
Cc: "Oliver Upton" <oupton@kernel.org>,
"Marc Zyngier" <maz@kernel.org>,
kvmarm@lists.linux.dev
Subject: Re: [PATCH v3 4/8] KVM: arm64: Move PSCI helper functions to a shared header
Date: Fri, 26 Jun 2026 07:16:42 +0000 [thread overview]
Message-ID: <20260626071642.C7C821F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260626070408.3420953-5-fuad.tabba@linux.dev>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly shared header `include/kvm/arm_psci.h` references functions without including their defining headers (`<asm/kvm_emulate.h>` and `<linux/wordpart.h>`), violating the practice of self-contained headers.
--
commit 6015f90f953617e9e81e02b97f5532daaa5dfdd7
Author: Fuad Tabba <fuad.tabba@linux.dev>
KVM: arm64: Move PSCI helper functions to a shared header
This commit moves kvm_psci_valid_affinity(), kvm_psci_narrow_to_32bit(),
and psci_affinity_mask() from psci.c to the shared include/kvm/arm_psci.h
header. This prepares the helpers for use in protected-guest PSCI calls
at EL2.
> diff --git a/include/kvm/arm_psci.h b/include/kvm/arm_psci.h
> index cbaec804eb839..f86a006d67136 100644
> --- a/include/kvm/arm_psci.h
> +++ b/include/kvm/arm_psci.h
[ ... ]
> +/* Narrow the PSCI register arguments (r1 to r3) to 32 bits. */
> +static inline void kvm_psci_narrow_to_32bit(struct kvm_vcpu *vcpu)
> +{
> + int i;
> +
> + /*
> + * Zero the input registers' upper 32 bits. They will be fully
> + * zeroed on exit, so we're fine changing them in place.
> + */
> + for (i = 1; i < 4; i++)
> + vcpu_set_reg(vcpu, i, lower_32_bits(vcpu_get_reg(vcpu, i)));
> +}
[Severity: Low]
Does this new shared header need to include asm/kvm_emulate.h and
linux/wordpart.h to remain self-contained?
This inline function relies on lower_32_bits(), vcpu_get_reg(), and
vcpu_set_reg(), but the definitions are not directly included here.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260626070408.3420953-1-fuad.tabba@linux.dev?part=4
next prev parent reply other threads:[~2026-06-26 7:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 7:04 [PATCH v3 0/8] KVM: arm64: Rework pKVM vCPU state synchronisation Fuad Tabba
2026-06-26 7:04 ` [PATCH v3 1/8] KVM: arm64: Extract MPIDR computation into a shared header Fuad Tabba
2026-06-26 7:04 ` [PATCH v3 2/8] KVM: arm64: Make vcpu_{read,write}_sys_reg available to HYP code Fuad Tabba
2026-06-26 7:04 ` [PATCH v3 3/8] KVM: arm64: Factor out reusable vCPU reset helpers Fuad Tabba
2026-06-26 7:04 ` [PATCH v3 4/8] KVM: arm64: Move PSCI helper functions to a shared header Fuad Tabba
2026-06-26 7:16 ` sashiko-bot [this message]
2026-06-26 7:20 ` Fuad Tabba
2026-06-26 7:04 ` [PATCH v3 5/8] KVM: arm64: Add host and hypervisor vCPU lookup primitives Fuad Tabba
2026-06-26 7:04 ` [PATCH v3 6/8] KVM: arm64: Minimise EL2's exposure of host VGIC state during world switch Fuad Tabba
2026-06-26 7:24 ` sashiko-bot
2026-06-26 7:30 ` Fuad Tabba
2026-06-26 7:04 ` [PATCH v3 7/8] KVM: arm64: Add primitives to flush/sync the VGIC state at EL2 Fuad Tabba
2026-06-26 7:27 ` sashiko-bot
2026-06-26 7:33 ` Fuad Tabba
2026-06-26 7:04 ` [PATCH v3 8/8] KVM: arm64: Implement lazy vCPU state sync for non-protected guests Fuad Tabba
2026-06-26 7:26 ` Vincent Donnefort
2026-06-26 7:29 ` sashiko-bot
2026-06-26 7:36 ` 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=20260626071642.C7C821F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=fuad.tabba@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox