From: Roman Kisel <romank@linux.microsoft.com>
To: sudeep.holla@arm.com
Cc: anirudh@anirudhrb.com, linux-arm-kernel@lists.infradead.org,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
lpieralisi@kernel.org, mark.rutland@arm.com
Subject: Re: [PATCH] firmware: smccc: support both conduits for getting hyp UUID
Date: Tue, 10 Jun 2025 09:06:48 -0700 [thread overview]
Message-ID: <20250610160656.11984-1-romank@linux.microsoft.com> (raw)
In-Reply-To: <20250605-kickass-cerulean-honeybee-aa0cba@sudeepholla>
> (sorry for the delay, found the patch in the spam 🙁)
"b4" shows the the mail server used for the patch submission
doesn't pass the DKIM check, so finding the patch in the spam seems
expected :) Thanks for your help!
>
> On Wed, May 21, 2025 at 09:40:48AM +0000, Anirudh Rayabharam wrote:
>> From: Anirudh Rayabharam (Microsoft) <anirudh@anirudhrb.com>
>>
>> When Linux is running as the root partition under Microsoft Hypervisor
>> (MSHV) a.k.a Hyper-V, smc is used as the conduit for smc calls.
>>
>> Extend arm_smccc_hypervisor_has_uuid() to support this usecase. Use
>> arm_smccc_1_1_invoke to retrieve and use the appropriate conduit instead
>> of supporting only hvc.
>>
>> Boot tested on MSHV guest, MSHV root & KVM guest.
>>
>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
>
> Are they any dependent patches or series using this ? Do you plan to
> route it via KVM tree if there are any dependency. Or else I can push
> it through (arm-)soc tree. Let me know.
Anirudh had been OOF for some time and would be for another
week iiuc so I thought I'd reply.
The patch this depends on is 13423063c7cb
("arm64: kvm, smccc: Introduce and use API for getting hypervisor UUID"),
and this patch has already been pulled into the Linus'es tree.
As for routing, (arm-)soc should be good it appears as the change
is contained within the firmware drivers path. Although I'd trust more to your,
Arnd's or Wei's opinion than mine!
>
> --
> Regards,
> Sudeep
next prev parent reply other threads:[~2025-06-10 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 9:40 [PATCH] firmware: smccc: support both conduits for getting hyp UUID Anirudh Rayabharam
2025-06-04 21:45 ` Roman Kisel
2025-06-05 15:33 ` Sudeep Holla
2025-06-10 16:06 ` Roman Kisel [this message]
2025-06-11 12:52 ` Sudeep Holla
2025-06-18 12:20 ` Anirudh Rayabharam
2025-06-18 12:20 ` Anirudh Rayabharam
2025-06-18 17:57 ` Roman Kisel
2025-06-27 9:59 ` Sudeep Holla
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=20250610160656.11984-1-romank@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=anirudh@anirudhrb.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=sudeep.holla@arm.com \
/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