From: Greg KH <gregkh@linuxfoundation.org>
To: Rishi Chhibber <rishi.chhibber@broadcom.com>
Cc: arnd@arndb.de, bryan-bt.tan@broadcom.com,
vishnu.dasa@broadcom.com, corbet@lwn.net,
skhan@linuxfoundation.org, shuah@kernel.org,
rdunlap@infradead.org, bcm-kernel-feedback-list@broadcom.com,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, ajay.kaher@broadcom.com,
alexey.makhalov@broadcom.com,
vamsi-krishna.brahmajosyula@broadcom.com, yin.ding@broadcom.com,
tapas.kundu@broadcom.com
Subject: Re: [PATCH v3 0/4] misc: vmw_zerocopy: VMware zero-copy buffer sharing driver
Date: Thu, 1 Oct 2026 14:00:06 +0200 [thread overview]
Message-ID: <2026100137-molasses-rented-5c88@gregkh> (raw)
In-Reply-To: <cover.1789413109.git.rishi.chhibber@broadcom.com>
On Mon, Sep 14, 2026 at 01:22:05PM -0700, Rishi Chhibber wrote:
> Summary of changes:
> - 1/4 reserves a VMCI datagram resource id for the hypervisor-side
> zero-copy service
> - 2/4 adds the vmw_zerocopy driver: /dev/vmw_zc, a single ioctl, page
> pinning and the VMCI datagram transport
> - 3/4 documents the userspace interface
> - 4/4 adds a kselftest covering the ioctl input-validation paths
>
> This series adds a misc character device, /dev/vmw_zc, that lets guest
> userspace hand a buffer to a VMware hypervisor-side peer without copying
> it. The driver pins the user pages, collects their guest physical frame
> numbers and sends that list over a VMCI datagram; the hypervisor then
> reads the buffer directly out of guest memory. An optional metadata
> buffer is pinned writable so the peer can return a result through the
> same mechanism.
You are going to need to get the -mm maintainers/developers to sign off
on this thing before I can accept it due to your "fun" use of memory
buffers in here.
thanks,
greg k-h
prev parent reply other threads:[~2026-10-01 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 20:22 Rishi Chhibber
2026-09-14 20:22 ` [PATCH v3 1/4] misc: vmw_vmci: Reserve a datagram resource id for zero-copy buffer sharing Rishi Chhibber
2026-09-14 20:22 ` [PATCH v3 2/4] misc: vmw_zerocopy: Add VMware zero-copy buffer sharing driver Rishi Chhibber
2026-09-15 7:13 ` Greg KH
2026-09-14 20:22 ` [PATCH v3 3/4] Documentation: misc: Add vmw_zerocopy driver documentation Rishi Chhibber
2026-09-14 20:22 ` [PATCH v3 4/4] selftests: misc: Add vmw_zerocopy selftest Rishi Chhibber
2026-10-01 12:00 ` Greg KH [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=2026100137-molasses-rented-5c88@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bryan-bt.tan@broadcom.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rishi.chhibber@broadcom.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tapas.kundu@broadcom.com \
--cc=vamsi-krishna.brahmajosyula@broadcom.com \
--cc=vishnu.dasa@broadcom.com \
--cc=yin.ding@broadcom.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
all inboxes | Powered by JetHome®