From: Roman Kisel <romank@linux.microsoft.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
Jack Thomson <jackabt.amazon@gmail.com>
Cc: mark.rutland@arm.com, lpieralisi@kernel.org, arnd@arndb.de,
wei.liu@kernel.org, mhklinux@outlook.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, maz@kernel.org,
oliver.upton@linux.dev, kvmarm@lists.linux.dev,
roypat@amazon.com, Jack Thomson <jackabt@amazon.com>
Subject: Re: [PATCH] arm64: kvm, smccc: Fix vendor uuid
Date: Mon, 21 Jul 2025 10:20:54 -0700 [thread overview]
Message-ID: <55e5f8d2-2b81-4883-a9ac-ad1a426c4222@linux.microsoft.com> (raw)
In-Reply-To: <20250721-proficient-carrot-cockatoo-393ae1@sudeepholla>
On 7/21/2025 9:15 AM, Sudeep Holla wrote:
> (I can't see this original patch in my mailbox, got only Marc's response)
>
> On Mon, Jul 21, 2025 at 02:05:58PM +0100, Jack Thomson wrote:
>> From: Jack Thomson <jackabt@amazon.com>
>>
>> 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.
>>
>> This patch updates the parameters to the macro to generate a UUID which
>> matches the previous value, and re-establish backwards compatibility
>> with older guest kernels.
>>
>
> Nice catch. This is result of classic confusion with UUID and GUID especially
> coming from Microsoft who tend to use GUID more.
>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
>
> This also makes me wonder if the initialisation in arch/arm64/hyperv/mshyperv.c
> is also wrong or may be that's correct only MS guys can confirm as I couldn't
> find the UUID string for that.
MUCH appreciated!! Apologies for that miss in testing of the older
kernels. I'll check on our side and will fix what needs fixing.
>
--
Thank you,
Roman
next prev parent reply other threads:[~2025-07-21 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 13:05 [PATCH] arm64: kvm, smccc: Fix vendor uuid Jack Thomson
2025-07-21 15:59 ` Marc Zyngier
2025-07-21 17:14 ` Will Deacon
2025-07-21 17:27 ` Roman Kisel
2025-07-21 16:15 ` Sudeep Holla
2025-07-21 17:20 ` Roman Kisel [this message]
2025-07-21 17:45 ` 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=55e5f8d2-2b81-4883-a9ac-ad1a426c4222@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=arnd@arndb.de \
--cc=jackabt.amazon@gmail.com \
--cc=jackabt@amazon.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mhklinux@outlook.com \
--cc=oliver.upton@linux.dev \
--cc=roypat@amazon.com \
--cc=sudeep.holla@arm.com \
--cc=wei.liu@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