[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175311813171.3793918.5949198639937646656.b4-ty@kernel.org>
Date: Mon, 21 Jul 2025 18:45:48 +0100
From: Will Deacon <will@...nel.org>
To: mark.rutland@....com,
lpieralisi@...nel.org,
sudeep.holla@....com,
arnd@...db.de,
wei.liu@...nel.org,
romank@...ux.microsoft.com,
mhklinux@...look.com,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
maz@...nel.org,
oliver.upton@...ux.dev,
kvmarm@...ts.linux.dev,
Jack Thomson <jackabt.amazon@...il.com>
Cc: catalin.marinas@....com,
kernel-team@...roid.com,
Will Deacon <will@...nel.org>,
roypat@...zon.com,
Jack Thomson <jackabt@...zon.com>
Subject: Re: [PATCH] arm64: kvm, smccc: Fix vendor uuid
On Mon, 21 Jul 2025 14:05:58 +0100, Jack Thomson wrote:
> Commit 13423063c7cb ("arm64: kvm, smccc: Introduce and use API for
> getting hypervisor UUID") replaced the explicit register constants
> with the UUID_INIT macro. However, there is an endian issue, meaning
> the UUID generated and used in the handshake didn't match UUID prior to
> the commit.
>
> The change in UUID causes the SMCCC vendor handshake to fail with older
> guest kernels, meaning devices such as PTP were not available in the
> guest.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: kvm, smccc: Fix vendor uuid
https://git.kernel.org/arm64/c/ab1612211532
There was a stray "getting hypervisor UUID")" line in the original
commit message after the Fixes: tag, so I dropped that bit.
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists