From: Jorgen Hansen <jhansen@vmware.com>
To: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org
Cc: pv-drivers@vmware.com, gregkh@linuxfoundation.org,
Jorgen Hansen <jhansen@vmware.com>
Subject: [PATCH v3 0/8] VMCI: dma dg: Add support for DMA datagrams
Date: Mon, 7 Feb 2022 02:27:17 -0800 [thread overview]
Message-ID: <20220207102725.2742-1-jhansen@vmware.com> (raw)
A new version of the VMCI device will introduce two new major changes:
- support MMIO access to device registers
- support send/receive of datagrams using DMA transfers instead of
ioread8_rep/iowrite8_rep operations
This patch series updates the VMCI driver to support these new
features while maintaining backwards compatibility.
The DMA based datagram operations use a send and a receive buffer
allocated at module load time. The buffer contains a header
describing the layout of the buffer followed by either an SG list or
inline data. The header also contains a flag indicating whether the
buffer is currently owned by the driver or the device. Both for send
and receive, the driver will initialize the buffer, transfer ownership
to the device by writing the buffer address to a register, and then
wait for the ownership to be transferred back. The device will
generate an interrupt when this happens.
v2 (fixes issues flagged by kernel test robot <lkp@intel.com>):
- changed type of mmio_base to void __iomem *
- made vmci_read_reg, vmci_write_reg and vmci_write_data static functions
v3:
- removed log messages for page size and BAR resources
Jorgen Hansen (8):
VMCI: dma dg: whitespace formatting change for vmci register defines
VMCI: dma dg: add MMIO access to registers
VMCI: dma dg: detect DMA datagram capability
VMCI: dma dg: set OS page size
VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
VMCI: dma dg: allocate send and receive buffers for DMA datagrams
VMCI: dma dg: add support for DMA datagrams sends
VMCI: dma dg: add support for DMA datagrams receive
drivers/misc/vmw_vmci/vmci_guest.c | 335 ++++++++++++++++++++++++-----
include/linux/vmw_vmci_defs.h | 84 +++++++-
2 files changed, 355 insertions(+), 64 deletions(-)
--
2.25.1
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next reply other threads:[~2022-02-07 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 10:27 Jorgen Hansen [this message]
2022-02-07 10:27 ` [PATCH v3 1/8] VMCI: dma dg: whitespace formatting change for vmci register defines Jorgen Hansen
2022-02-07 10:27 ` [PATCH v3 2/8] VMCI: dma dg: add MMIO access to registers Jorgen Hansen
2022-02-07 10:27 ` [PATCH v3 3/8] VMCI: dma dg: detect DMA datagram capability Jorgen Hansen
2022-02-07 10:27 ` [PATCH v3 4/8] VMCI: dma dg: set OS page size Jorgen Hansen
2022-02-07 10:27 ` [PATCH v3 5/8] VMCI: dma dg: register dummy IRQ handlers for DMA datagrams Jorgen Hansen
2022-02-07 10:27 ` [PATCH v3 6/8] VMCI: dma dg: allocate send and receive buffers " Jorgen Hansen
2022-02-07 10:27 ` [PATCH v3 7/8] VMCI: dma dg: add support for DMA datagrams sends Jorgen Hansen
2022-02-07 10:27 ` [PATCH v3 8/8] VMCI: dma dg: add support for DMA datagrams receive Jorgen Hansen
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=20220207102725.2742-1-jhansen@vmware.com \
--to=jhansen@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).