[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250611-wandering-juicy-magpie-ed7f46@sudeepholla>
Date: Wed, 11 Jun 2025 13:52:32 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Roman Kisel <romank@...ux.microsoft.com>
Cc: anirudh@...rudhrb.com, linux-arm-kernel@...ts.infradead.org,
Sudeep Holla <sudeep.holla@....com>, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, lpieralisi@...nel.org,
mark.rutland@....com
Subject: Re: [PATCH] firmware: smccc: support both conduits for getting hyp
UUID
On Tue, Jun 10, 2025 at 09:06:48AM -0700, Roman Kisel wrote:
> > (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!
>
Thought so looking at the header but I just have very basic knowledge
there, so couldn't comment.
> >
> > On Wed, May 21, 2025 at 09:40:48AM +0000, Anirudh Rayabharam wrote:
> >> From: Anirudh Rayabharam (Microsoft) <anirudh@...rudhrb.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@....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.
>
Had a quick look at the commit to refresh my memory and as you mentioned
it is new feature. I was checking to see if this is a fix.
> 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!
>
I will queue this once I start collecting patches for v6.17 in 1/2 weeks'
time, so expect silence until then 😄.
--
Regards,
Sudeep
Powered by blists - more mailing lists