mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Easwar Hariharan <easwar.hariharan@linux.microsoft.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: easwar.hariharan@linux.microsoft.com,
	Nuno Das Neves <nunodasneves@linux.microsoft.com>,
	linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org, kys@microsoft.com,
	haiyangz@microsoft.com, mhklinux@outlook.com,
	decui@microsoft.com, arnd@arndb.de
Subject: Re: [PATCH] mshv: Add support for a new parent partition configuration
Date: Tue, 19 Aug 2025 10:29:33 -0700	[thread overview]
Message-ID: <2393d3f9-3d13-4e62-ad3d-b9158665af12@linux.microsoft.com> (raw)
In-Reply-To: <aKSyzopAGQhM61B0@liuwe-devbox-ubuntu-v2.tail21d00.ts.net>

On 8/19/2025 10:22 AM, Wei Liu wrote:
> On Tue, Aug 19, 2025 at 09:17:27AM -0700, Easwar Hariharan wrote:
>> On 8/19/2025 12:29 AM, Nuno Das Neves wrote:
>>> Detect booting as an "L1VH" partition. This is a new scenario very
>>> similar to root partition where the mshv_root driver can be used to
>>> create and manage guest partitions.
>>>
>>> It mostly works the same as root partition, but there are some
>>> differences in how various features are handled. hv_l1vh_partition()
>>> is introduced to handle these cases. Add hv_parent_partition()
>>> which returns true for either case, replacing some hv_root_partition()
>>> checks.
>>>
>>> Signed-off-by: Nuno Das Neves <nunodasneves@linux.microsoft.com>
>>
>> Seems the plurality of subject prefixes for drivers/hv files has been "Drivers: hv"
>> so far, including the 2 commits for drivers/hv/mshv*. Are you planning to change
>> the standard for mshv driver going forward?
> 
> IMO it is okay to have a different prefix to call out the commits that
> are relevant to the mshv driver. This eases the burden for anyone
> porting the changes to a different kernel tree. We may also touch many
> different parts of the codebase (though not in this particular patch).
> 
> Wei

It's fine either way for me, I was trying to understand if it was an oversight or
intentional.

- Easwar (he/him)

  reply	other threads:[~2025-08-19 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19  7:29 Nuno Das Neves
2025-08-19 16:17 ` Easwar Hariharan
2025-08-19 17:22   ` Wei Liu
2025-08-19 17:29     ` Easwar Hariharan [this message]
2025-08-19 16:46 ` Wei Liu
2025-08-31 15:12 ` Michael Kelley

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=2393d3f9-3d13-4e62-ad3d-b9158665af12@linux.microsoft.com \
    --to=easwar.hariharan@linux.microsoft.com \
    --cc=arnd@arndb.de \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhklinux@outlook.com \
    --cc=nunodasneves@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®