From: Wei Liu <wei.liu@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Wei Liu <wei.liu@kernel.org>,
Michael Kelley <mikelley@microsoft.com>,
kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, decui@microsoft.com,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-hyperv@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Documentation: hyperv: Add basic info on Hyper-V enlightenments
Date: Sun, 17 Jul 2022 23:14:58 +0000 [thread overview]
Message-ID: <20220717231458.zcapml7bfccw2pjw@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <8735f44w27.fsf@meer.lwn.net>
On Wed, Jul 13, 2022 at 02:06:08PM -0600, Jonathan Corbet wrote:
> Wei Liu <wei.liu@kernel.org> writes:
>
> > On Mon, Jul 11, 2022 at 10:48:21AM -0700, Michael Kelley wrote:
> >> This documentation is a high level overview to explain the basics
> >> of Linux running as a guest on Hyper-V. The intent is to document
> >> the forest, not the trees. The Hyper-V Top Level Functional Spec
> >> provides conceptual material and API details for the core Hyper-V
> >> hypervisor, and this documentation provides additional info on
> >> how that functionality is applied to Linux. Also, there's no
> >> public documentation on VMbus or the VMbus synthetic devices, so
> >> this documentation helps fill that gap at a conceptual level. This
> >> documentation is not API-level documentation, which can be seen
> >> in the code and associated comments.
> >>
> >> More topics will be added in future patches, including:
> >>
> >> * Miscellaneous synthetic devices like KVP, timesync, VSS, etc.
> >> * Virtual PCI support
> >> * Isolated/Confidential VMs
> >> * UIO driver
> >>
> >> If you think I'm missing a topic that fits into the overall
> >> approach as described, feel free to suggest text, or let me
> >> know and I can add it to my list.
> >>
> >> Changes in v2:
> >> * Updated clocks.rst to use section hierarchy that matches
> >> overview.rst and vmbus.rst [Wei Liu]
> >>
> >> Michael Kelley (3):
> >> Documentation: hyperv: Add overview of Hyper-V enlightenments
> >> Documentation: hyperv: Add overview of VMbus
> >> Documentation: hyperv: Add overview of clocks and timers
> >
> > Content-wise all patches look good to me.
> >
> > Jonathan, let me know how you would like to handle this series. I'm
> > happy to carry them in hyperv-next.
>
> I went ahead and applied them while I was in the neighborhood.
Thanks!
prev parent reply other threads:[~2022-07-17 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 17:48 [PATCH v2 0/3] Documentation: hyperv: Add basic info on Hyper-V enlightenments Michael Kelley
2022-07-11 17:48 ` [PATCH v2 1/3] Documentation: hyperv: Add overview of " Michael Kelley
2022-07-11 17:48 ` [PATCH v2 2/3] Documentation: hyperv: Add overview of VMbus Michael Kelley
2022-07-11 17:48 ` [PATCH v2 3/3] Documentation: hyperv: Add overview of clocks and timers Michael Kelley
2022-07-11 18:56 ` [PATCH v2 0/3] Documentation: hyperv: Add basic info on Hyper-V enlightenments Wei Liu
2022-07-13 20:06 ` Jonathan Corbet
2022-07-17 23:14 ` Wei Liu [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=20220717231458.zcapml7bfccw2pjw@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=corbet@lwn.net \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=sthemmin@microsoft.com \
/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