mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Nuno Das Neves <nunodasneves@linux.microsoft.com>
Cc: Naman Jain <namjain@linux.microsoft.com>,
	"K . Y . Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
	eahariha@linux.microsoft.com,
	Roman Kisel <romank@linux.microsoft.com>,
	Anirudh Rayabharam <anrayabh@linux.microsoft.com>,
	Saurabh Sengar <ssengar@linux.microsoft.com>,
	Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>,
	ALOK TIWARI <alok.a.tiwari@oracle.com>,
	linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org
Subject: Re: [PATCH v5 2/2] Drivers: hv: Introduce mshv_vtl driver
Date: Wed, 11 Jun 2025 11:00:11 -0700	[thread overview]
Message-ID: <6be766a4-c983-4316-a07b-fd96238191e4@linux.microsoft.com> (raw)
In-Reply-To: <2f2a252f-c2cb-40ee-a416-c07fd120dd49@linux.microsoft.com>

On 6/11/2025 9:46 AM, Nuno Das Neves wrote:
> On 6/11/2025 12:27 AM, Naman Jain wrote:
>> Provide an interface for Virtual Machine Monitor like OpenVMM and its
>> use as OpenHCL paravisor to control VTL0 (Virtual trust Level).
>> Expose devices and support IOCTLs for features like VTL creation,
>> VTL0 memory management, context switch, making hypercalls,
>> mapping VTL0 address space to VTL2 userspace, getting new VMBus
>> messages and channel events in VTL2 etc.
>>
>> Co-developed-by: Roman Kisel <romank@linux.microsoft.com>
>> Signed-off-by: Roman Kisel <romank@linux.microsoft.com>
>> Co-developed-by: Saurabh Sengar <ssengar@linux.microsoft.com>
>> Signed-off-by: Saurabh Sengar <ssengar@linux.microsoft.com>
>> Reviewed-by: Roman Kisel <romank@linux.microsoft.com>
>> Reviewed-by: Alok Tiwari <alok.a.tiwari@oracle.com>
>> Message-ID: <20250512140432.2387503-3-namjain@linux.microsoft.com>
>> Reviewed-by: Saurabh Sengar <ssengar@linux.microsoft.com>
>> Signed-off-by: Naman Jain <namjain@linux.microsoft.com>
>> ---
>>  drivers/hv/Kconfig          |   23 +
>>  drivers/hv/Makefile         |    7 +-
>>  drivers/hv/mshv_vtl.h       |   52 +
>>  drivers/hv/mshv_vtl_main.c  | 1783 +++++++++++++++++++++++++++++++++++
>>  include/hyperv/hvgdk_mini.h |   81 ++
>>  include/hyperv/hvhdk.h      |    1 +
>>  include/uapi/linux/mshv.h   |   82 ++
>>  7 files changed, 2028 insertions(+), 1 deletion(-)
>>  create mode 100644 drivers/hv/mshv_vtl.h
>>  create mode 100644 drivers/hv/mshv_vtl_main.c
>>

<snip>

> 
> Reviewed-by: Nuno Das Neves <nunodasneves@linux.microsoft.com>

Hi Nuno,

In the future, please trim unnecessary context, example above, following 
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#use-trimmed-interleaved-replies-in-email-discussions

"Similarly, please trim all unneeded quotations that aren’t relevant to your reply.
This makes responses easier to find, and saves time and space. For more details see:
 http://daringfireball.net/2007/07/on_top"

Thanks,
Easwar (he/him)

  reply	other threads:[~2025-06-11 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11  7:27 [PATCH v5 0/2] Drivers: hv: Introduce new driver - mshv_vtl Naman Jain
2025-06-11  7:27 ` [PATCH v5 1/2] Drivers: hv: Export some symbols for mshv_vtl Naman Jain
2025-06-11  7:27 ` [PATCH v5 2/2] Drivers: hv: Introduce mshv_vtl driver Naman Jain
2025-06-11 16:46   ` Nuno Das Neves
2025-06-11 18:00     ` Easwar Hariharan [this message]
2025-07-09 17:19   ` Michael Kelley
2025-07-10  9:01     ` Naman Jain
2025-07-17 16:21     ` Nuno Das Neves
2025-07-18  4:36     ` Naman Jain
2025-07-18 15:07       ` Michael Kelley
2025-07-22 11:09         ` Naman Jain
2025-07-22 17:09           ` Michael Kelley
2025-07-23  9:58             ` Naman Jain
2025-07-23 14:13               ` Michael Kelley
2025-07-19 18:30   ` Markus Elfring
2025-07-22  9:16     ` Naman Jain

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=6be766a4-c983-4316-a07b-fd96238191e4@linux.microsoft.com \
    --to=eahariha@linux.microsoft.com \
    --cc=alok.a.tiwari@oracle.com \
    --cc=anrayabh@linux.microsoft.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=namjain@linux.microsoft.com \
    --cc=nunodasneves@linux.microsoft.com \
    --cc=romank@linux.microsoft.com \
    --cc=skinsburskii@linux.microsoft.com \
    --cc=ssengar@linux.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

all inboxes | Powered by JetHome®