From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Will Deacon <will@kernel.org>
Cc: kvmarm@lists.linux.dev, kvm@vger.kernel.org, maz@kernel.org,
oupton@kernel.org, aneesh.kumar@kernel.org, steven.price@arm.com,
linux-kernel@vger.kernel.org, alexandru.elisei@arm.com,
tabba@google.com
Subject: Re: [kvmtool PATCH v5 02/15] update_headers: arm64: Track psci.h for PSCI definitions
Date: Fri, 27 Feb 2026 10:23:52 +0000 [thread overview]
Message-ID: <90bac820-7c15-4528-9d7f-3a8a4a67fb10@arm.com> (raw)
In-Reply-To: <aYoCiXg8pSC_bwIv@willie-the-truck>
On 09/02/2026 15:51, Will Deacon wrote:
> On Thu, Jan 08, 2026 at 05:57:40PM +0000, Suzuki K Poulose wrote:
>> Track UAPI psci.h for PSCI definitions
>>
>> Reviewed-by: Marc Zyngier <maz@kernel.org>
>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>> ---
>> util/update_headers.sh | 17 ++++++++++-------
>> 1 file changed, 10 insertions(+), 7 deletions(-)
>>
>> diff --git a/util/update_headers.sh b/util/update_headers.sh
>> index af75ca36..9fe782a2 100755
>> --- a/util/update_headers.sh
>> +++ b/util/update_headers.sh
>> @@ -37,13 +37,16 @@ done
>>
>> unset KVMTOOL_PATH
>>
>> -copy_optional_arch () {
>> - local src="$LINUX_ROOT/arch/$arch/include/uapi/$1"
>> +copy_arm64_headers () {
>> + local uapi_asm_hdr="$LINUX_ROOT/arch/$arch/include/uapi/asm"
>>
>> - if [ -r "$src" ]
>> - then
>> - cp -- "$src" "$KVMTOOL_PATH/include/asm/"
>> - fi
>> + for f in sve_context.h psci.h
>> + do
>> + if [ -r "$uapi_asm_hdr/$f" ]
>> + then
>> + cp -- "$uapi_asm_hdr/$f" "$KVMTOOL_PATH/include/asm/"
>> + fi
>> + done
>
> This doesn't make sense to me as I don't think we've ever had an
> arm64 uapi/asm/psci.h. You presumably want linux/psci.h (which is what
> the next patch pulls in), but then I don't understand how that worked
> with the change you've got here :/
Yikes, it is in the generic uapi. I will fix this in the next iteration.
May be we could add a Warning message in the util script for missing
header files to catch such errors.
>
> For now, I'll apply the first patch and then update the headers to 6.19
> myself using the current script (as other folks need them updating too).
Thanks
Suzuki
>
> Will
next prev parent reply other threads:[~2026-02-27 10:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 17:57 [kvmtool PATCH v5 00/15] arm64: Handle PSCI calls in userspace Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 01/15] Allow pausing the VM from vcpu thread Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 02/15] update_headers: arm64: Track psci.h for PSCI definitions Suzuki K Poulose
2026-02-09 15:51 ` Will Deacon
2026-02-27 10:23 ` Suzuki K Poulose [this message]
2026-01-08 17:57 ` [kvmtool PATCH v5 03/15] update headers: Linux v6.18 Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 04/15] Import arm-smccc.h from " Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 05/15] arm64: Stash kvm_vcpu_init for later use Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 06/15] arm64: Use KVM_SET_MP_STATE ioctl to power off non-boot vCPUs Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 07/15] arm64: Expose ARM64_CORE_REG() for general use Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 08/15] arm64: Add support for finding vCPU for given MPIDR Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 09/15] arm64: Add skeleton implementation for PSCI Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 10/15] arm64: psci: Implement CPU_SUSPEND Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 11/15] arm64: psci: Implement CPU_ON Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 12/15] arm64: psci: Implement AFFINITY_INFO Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 13/15] arm64: psci: Implement MIGRATE_INFO_TYPE Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 14/15] arm64: psci: Implement SYSTEM_{OFF,RESET} Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 15/15] arm64: smccc: Start sending PSCI to userspace Suzuki K Poulose
2026-02-09 16:25 ` [kvmtool PATCH v5 00/15] arm64: Handle PSCI calls in userspace Will Deacon
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=90bac820-7c15-4528-9d7f-3a8a4a67fb10@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexandru.elisei@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=steven.price@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®