Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Fuad Tabba" <fuad.tabba@linux.dev>
Cc: "Marc Zyngier" <maz@kernel.org>,
	kvmarm@lists.linux.dev, "Oliver Upton" <oupton@kernel.org>
Subject: Re: [PATCH v6 4/8] KVM: arm64: Move PSCI helper functions to a shared header
Date: Wed, 15 Jul 2026 08:24:10 +0000	[thread overview]
Message-ID: <20260715082411.3987F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260715081238.1891918-5-fuad.tabba@linux.dev>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The header `include/kvm/arm_psci.h` is not self-contained because it uses `vcpu_set_reg()` and `vcpu_get_reg()` without including `<asm/kvm_emulate.h>`.
--

--- Patch [4]: [PATCH v6 4/8] KVM: arm64: Move PSCI helper functions to a shared header ---
(Note: The format of this report has been altered to a free-form summary without direct patch quotation due to automated system recitation restrictions.)

commit 41ab99d154503d49e14931a3e9bb6c067e760b44
Author: Fuad Tabba <fuad.tabba@linux.dev>

KVM: arm64: Move PSCI helper functions to a shared header

This patch moves several PSCI helper functions out of psci.c and into the
shared include/kvm/arm_psci.h header. It renames the file-local
psci_affinity_mask() to kvm_psci_affinity_mask() to support follow-up work
for protected-guest PSCI calls.

[Severity: Low]
In the newly moved kvm_psci_narrow_to_32bit() function within
include/kvm/arm_psci.h, the code makes use of vcpu_set_reg() and
vcpu_get_reg(). Does this new header location need an explicit include
for asm/kvm_emulate.h to ensure it remains self-contained?

If a C file includes kvm/arm_psci.h without having already included
asm/kvm_emulate.h, it looks like it might lead to a build failure due to
missing function declarations.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260715081238.1891918-1-fuad.tabba@linux.dev?part=4

  reply	other threads:[~2026-07-15  8:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15  8:12 [PATCH v6 0/8] KVM: arm64: pKVM vCPU state management at EL2 Fuad Tabba
2026-07-15  8:12 ` [PATCH v6 1/8] KVM: arm64: Extract MPIDR computation into a shared header Fuad Tabba
2026-07-15  8:12 ` [PATCH v6 2/8] KVM: arm64: Make vcpu_{read,write}_sys_reg available to HYP code Fuad Tabba
2026-07-15  8:12 ` [PATCH v6 3/8] KVM: arm64: Factor out reusable vCPU reset helpers Fuad Tabba
2026-07-17 12:43   ` Steffen Eiden
2026-07-15  8:12 ` [PATCH v6 4/8] KVM: arm64: Move PSCI helper functions to a shared header Fuad Tabba
2026-07-15  8:24   ` sashiko-bot [this message]
2026-07-15  8:28     ` Fuad Tabba
2026-07-15  8:12 ` [PATCH v6 5/8] KVM: arm64: Add host and hypervisor vCPU lookup primitives Fuad Tabba
2026-07-15  8:12 ` [PATCH v6 6/8] KVM: arm64: Minimise EL2's exposure of host VGIC state during world switch Fuad Tabba
2026-07-15  8:37   ` sashiko-bot
2026-07-15  9:18     ` Fuad Tabba
2026-07-15  8:12 ` [PATCH v6 7/8] KVM: arm64: Add primitives to flush/sync the VGIC state at EL2 Fuad Tabba
2026-07-15  8:12 ` [PATCH v6 8/8] KVM: arm64: Implement lazy vCPU state sync for non-protected guests Fuad Tabba
2026-07-15  8:34   ` sashiko-bot
2026-07-15  9:20     ` 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=20260715082411.3987F1F000E9@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