From: Michael Kelley <mhklinux@outlook.com>
To: Naman Jain <namjain@linux.microsoft.com>,
"haiyangz@microsoft.com" <haiyangz@microsoft.com>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
"decui@microsoft.com" <decui@microsoft.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: RE: [PATCH 1/1] Documentation: hyperv: Update documentation for sending VMBus packets
Date: Fri, 9 Oct 2026 05:31:15 +0000 [thread overview]
Message-ID: <MN2PR02MB68632A2D7C859FF9BBFBA020D4922@MN2PR02MB6863.namprd02.prod.outlook.com> (raw)
In-Reply-To: <db1a6c90-f2d9-44e4-be4b-1dbc96c66691@linux.microsoft.com>
From: Naman Jain <namjain@linux.microsoft.com> Sent: Thursday, October 8, 2026 9:39 PM
>
> On 10/9/2026 8:36 AM, Michael Kelley wrote:
> > The functions for sending VMBus packets have been simplified.
> > vmbus_sendpacket_mpb_desc() can target multiple ranges, and
> > vmbus_sendpacket_pagebuffer() has been removed. Update the
> > documentation accordingly.
> >
> > Fixes: 45a442fe369e ("Drivers: hv: vmbus: Remove vmbus_sendpacket_pagebuffer()")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Michael Kelley <mhklinux@outlook.com>
> > ---
> > The Fixes: tag reflects the code change that was made. The
> > documentation update should have been included with the
> > original code change.
> >
> > Documentation/virt/hyperv/vmbus.rst | 13 ++++---------
> > 1 file changed, 4 insertions(+), 9 deletions(-)
> >
> > diff --git a/Documentation/virt/hyperv/vmbus.rst
> b/Documentation/virt/hyperv/vmbus.rst
> > index 654bb4849972..77a437969b49 100644
> > --- a/Documentation/virt/hyperv/vmbus.rst
> > +++ b/Documentation/virt/hyperv/vmbus.rst
> > @@ -137,18 +137,13 @@ control message contains a list of GPAs that describe the data
> > buffer. For example, the storvsc driver uses this approach to
> > specify the data buffers to/from which disk I/O is done.
> >
> > -Three functions exist to send VMBus channel messages:
> > +Two functions exist to send VMBus channel messages:
> >
> > 1. vmbus_sendpacket(): Control-only messages and messages with
> > embedded data -- no GPAs
> > -2. vmbus_sendpacket_pagebuffer(): Message with list of GPAs
> > - identifying data to transfer. An offset and length is
> > - associated with each GPA so that multiple discontinuous areas
> > - of guest memory can be targeted.
> > -3. vmbus_sendpacket_mpb_desc(): Message with list of GPAs
> > - identifying data to transfer. A single offset and length is
> > - associated with a list of GPAs. The GPAs must describe a
> > - single logical area of guest memory to be targeted.
> > +2. vmbus_sendpacket_mpb_desc(): Message with one or more data ranges
> > + to target. Each range consists of a single offset and length plus
> > + a list of GPAs that describe a logical area of guest memory.
> >
> > Historically, Linux guests have trusted Hyper-V to send well-formed
> > and valid messages, and Linux drivers for synthetic devices did not
>
> vmbus_sendpacket_getid() is also part of the exported VMBus API and has
> an active caller in pci-hyperv.c. It might be useful to include it here
> and explain that it uses the same packet format as vmbus_sendpacket(),
> but additionally returns the transaction ID assigned to the packet.
>
Good point. I'll add it. I know enough about the _getid() variant to
properly document it.
Michael
prev parent reply other threads:[~2026-10-09 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 3:06 Michael Kelley
2026-10-09 4:38 ` Naman Jain
2026-10-09 5:31 ` Michael Kelley [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=MN2PR02MB68632A2D7C859FF9BBFBA020D4922@MN2PR02MB6863.namprd02.prod.outlook.com \
--to=mhklinux@outlook.com \
--cc=corbet@lwn.net \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjain@linux.microsoft.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--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®