On Sat, Nov 15, 2025 at 01:09:12PM +0530, Anirudh Rayabharam wrote: > On Sat, Nov 15, 2025 at 06:22:40AM +0000, Wei Liu wrote: > > On Fri, Nov 14, 2025 at 09:58:52AM +0000, Anirudh Rayabharam wrote: > > > From: Anirudh Rayabharam (Microsoft) <[email protected]> > > > > > > Allow MSHV_ROOT_HVCALL IOCTL on the /dev/mshv fd. This IOCTL would > > > execute a passthrough hypercall targeting the root/parent partition > > > i.e. HV_PARTITION_ID_SELF. > > > > > > This will be useful for the VMM to query things like supported > > > synthetic processor features, supported VMM capabiliites etc. > > > > > > While at it, add HVCALL_GET_PARTITION_PROPERTY_EX to the allowed list of > > > passthrough hypercalls. > > > > > > Signed-off-by: Anirudh Rayabharam (Microsoft) <[email protected]> > > > > This doesn't apply to hyperv-next. What's its base? > > Hmmm... I remember doing this on hyperv-next. This the parent I see: > > commit f2329fd987a0da4759c307c46fd27c4d05bb7433 > Author: Naman Jain <[email protected]> > Date: Thu Nov 13 04:41:49 2025 +0000 > > Drivers: hv: Introduce mshv_vtl driver > > No worries, I can rebase it on hyperv-next and send it again.
I pulled in some patches from hyperv-fixes to hyperv-next. That's probably why. But you will see that eventually during a merge later anyway, so it is good to just rebase and resend. Wei > > Thanks, > Anirudh. >
