Linux-HyperV List
 help / color / mirror / Atom feed
From: Anirudh Rayabharam <anirudh@anirudhrb.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Dexuan Cui <decui@microsoft.com>, Long Li <longli@microsoft.com>,
	linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Drivers: hv: ioctl for self targeted passthrough hvcalls
Date: Mon, 24 Nov 2025 14:27:57 +0000	[thread overview]
Message-ID: <aSRrbfdMFYre4Z0c@anirudh-surface.localdomain> (raw)
In-Reply-To: <20251120065559.GA2858107@liuwe-devbox-debian-v2.local>

On Thu, Nov 20, 2025 at 06:55:59AM +0000, Wei Liu wrote:
> On Wed, Nov 19, 2025 at 05:17:08PM +0000, Anirudh Rayabharam wrote:
> > From: Anirudh Rayabharam (Microsoft) <anirudh@anirudhrb.com>
> > 
> > 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.
> > 
> > Since hypercalls targeting the host partition could potentially perform
> > privileged operations, allow only a limited set of hypercalls. To begin
> > with, allow only:
> > 
> > 	HVCALL_GET_PARTITION_PROPERTY
> > 	HVCALL_GET_PARTITION_PROPERTY_EX
> > 
> > Signed-off-by: Anirudh Rayabharam (Microsoft) <anirudh@anirudhrb.com>
> 
> Applied to hyperv-next.
> 
> I dropped one "inline" keyword that was not needed and modified the
> subject prefix to be "mshv".

Thanks!

Anirudh.

> 
> Wei

      reply	other threads:[~2025-11-24 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 17:17 [PATCH v3] Drivers: hv: ioctl for self targeted passthrough hvcalls Anirudh Rayabharam
2025-11-19 21:34 ` Wei Liu
2025-11-20  6:13   ` Anirudh Rayabharam
2025-11-19 23:09 ` Nuno Das Neves
2025-11-20  6:55 ` Wei Liu
2025-11-24 14:27   ` Anirudh Rayabharam [this message]

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=aSRrbfdMFYre4Z0c@anirudh-surface.localdomain \
    --to=anirudh@anirudhrb.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longli@microsoft.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