From: Jason Wang <jasowang@redhat.com>
To: Cindy Lu <lulu@redhat.com>,
mst@redhat.com, armbru@redhat.com, eblake@redhat.com,
cohuck@redhat.com
Cc: mhabets@solarflare.com, qemu-devel@nongnu.org,
rob.miller@broadcom.com, saugatm@xilinx.com, hanand@xilinx.com,
hch@infradead.org, eperezma@redhat.com, jgg@mellanox.com,
shahafs@mellanox.com, kevin.tian@intel.com, parav@mellanox.com,
vmireyno@marvell.com, cunming.liang@intel.com, gdawar@xilinx.com,
jiri@mellanox.com, xiao.w.wang@intel.com, stefanha@redhat.com,
zhihong.wang@intel.com, aadam@redhat.com, rdunlap@infradead.org,
maxime.coquelin@redhat.com, lingshan.zhu@intel.com
Subject: Re: [RFC v2 0/9] vDPA support in qemu
Date: Sat, 9 May 2020 11:10:47 +0800 [thread overview]
Message-ID: <05a79596-13c4-d66b-4014-32b0229914ab@redhat.com> (raw)
In-Reply-To: <20200508163218.22592-1-lulu@redhat.com>
On 2020/5/9 上午12:32, Cindy Lu wrote:
> vDPA device is a device that uses a datapath which complies with the
> virtio specifications with vendor specific control path. vDPA devices
> can be both physically located on the hardware or emulated by software.
> This RFC introduce the vDPA support in qemu
>
> change from v1
> separe the patch of introduce vhost_set_vring_ready method
I think you meant "separate"?
May worth to mention TODO:
1) vIOMMU support
2) live migration support
And it might be helpful if you can publish a github repo for people to try.
Thanks
> separe the patch of qemu_get_peer
> separe the patch of vhost_set_state
> intorduce the new macro specific for vDPA in configure
> intorduce the fuction to pass the fd from cmdline
> introduce the docmation in qemu-options.hx
> the other comments form last version
>
>
> Cindy Lu (3):
> net: introduce qemu_get_peer
> net: use the function qemu_get_peer
> virtio_net: introduce vhost_set_state
>
> Jason Wang (4):
> virtio-bus: introduce queue_enabled method
> virito-pci: implement queue_enabled method
> vhost_net: set vq ready during start if necessary
> vhost: introduce vhost_set_vring_ready method
>
> Tiwei Bie (2):
> vhost-vdpa: introduce vhost-vdpa net client
> vhost-vdpa: implement vhost-vdpa backend
>
> configure | 21 ++
> hw/net/vhost_net-stub.c | 4 +
> hw/net/vhost_net.c | 77 ++++-
> hw/net/virtio-net.c | 9 +
> hw/virtio/Makefile.objs | 1 +
> hw/virtio/vhost-backend.c | 5 +
> hw/virtio/vhost-vdpa.c | 447 ++++++++++++++++++++++++++++++
> hw/virtio/vhost.c | 14 +
> hw/virtio/virtio-pci.c | 13 +
> hw/virtio/virtio.c | 6 +
> include/hw/virtio/vhost-backend.h | 10 +-
> include/hw/virtio/vhost-vdpa.h | 25 ++
> include/hw/virtio/vhost.h | 1 +
> include/hw/virtio/virtio-bus.h | 4 +
> include/net/net.h | 1 +
> include/net/vhost-vdpa.h | 19 ++
> include/net/vhost_net.h | 4 +-
> net/Makefile.objs | 2 +-
> net/clients.h | 2 +
> net/net.c | 9 +
> net/vhost-vdpa.c | 227 +++++++++++++++
> qapi/net.json | 22 +-
> qemu-options.hx | 19 ++
> 23 files changed, 930 insertions(+), 12 deletions(-)
> create mode 100644 hw/virtio/vhost-vdpa.c
> create mode 100644 include/hw/virtio/vhost-vdpa.h
> create mode 100644 include/net/vhost-vdpa.h
> create mode 100644 net/vhost-vdpa.c
>
prev parent reply other threads:[~2020-05-09 3:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 16:32 [RFC v2 0/9] vDPA support in qemu Cindy Lu
2020-05-08 16:32 ` [RFC v2 1/9] net: introduce qemu_get_peer Cindy Lu
2020-05-08 16:32 ` [RFC v2 2/9] net: use the function qemu_get_peer Cindy Lu
2020-05-09 2:19 ` Jason Wang
2020-05-09 6:49 ` Cindy Lu
2020-05-08 16:32 ` [RFC v2 3/9] virtio_net: introduce vhost_set_state Cindy Lu
2020-05-09 2:25 ` Jason Wang
2020-05-09 7:08 ` Cindy Lu
2020-05-08 16:32 ` [RFC v2 4/9] vhost-vdpa: introduce vhost-vdpa net client Cindy Lu
2020-05-08 16:41 ` Eric Blake
2020-05-09 7:17 ` Cindy Lu
2020-05-09 2:40 ` Jason Wang
2020-05-09 7:31 ` Cindy Lu
2020-05-08 16:32 ` [RFC v2 5/9] vhost-vdpa: implement vhost-vdpa backend Cindy Lu
2020-05-09 3:00 ` Jason Wang
2020-05-09 3:07 ` Jason Wang
2020-05-09 8:14 ` Cindy Lu
2020-05-21 12:40 ` Stefan Hajnoczi
2020-05-25 15:33 ` Cindy Lu
2020-05-25 16:15 ` Stefan Hajnoczi
2020-05-08 16:32 ` [RFC v2 6/9] virtio-bus: introduce queue_enabled method Cindy Lu
2020-05-09 3:01 ` Jason Wang
2020-05-09 6:50 ` Cindy Lu
2020-05-08 16:32 ` [RFC v2 7/9] virito-pci: implement " Cindy Lu
2020-05-09 3:02 ` Jason Wang
2020-05-09 12:01 ` Philippe Mathieu-Daudé
2020-05-11 5:08 ` Cindy Lu
2020-05-08 16:32 ` [RFC v2 8/9] vhost_net: set vq ready during start if necessary Cindy Lu
2020-05-09 3:03 ` Jason Wang
2020-05-09 6:51 ` Cindy Lu
2020-05-08 16:32 ` [RFC v2 9/9] vhost: introduce vhost_set_vring_ready method Cindy Lu
2020-05-09 3:05 ` Jason Wang
2020-05-09 3:10 ` Jason Wang [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=05a79596-13c4-d66b-4014-32b0229914ab@redhat.com \
--to=jasowang@redhat.com \
--cc=aadam@redhat.com \
--cc=armbru@redhat.com \
--cc=cohuck@redhat.com \
--cc=cunming.liang@intel.com \
--cc=eblake@redhat.com \
--cc=eperezma@redhat.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=hch@infradead.org \
--cc=jgg@mellanox.com \
--cc=jiri@mellanox.com \
--cc=kevin.tian@intel.com \
--cc=lingshan.zhu@intel.com \
--cc=lulu@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mhabets@solarflare.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=qemu-devel@nongnu.org \
--cc=rdunlap@infradead.org \
--cc=rob.miller@broadcom.com \
--cc=saugatm@xilinx.com \
--cc=shahafs@mellanox.com \
--cc=stefanha@redhat.com \
--cc=vmireyno@marvell.com \
--cc=xiao.w.wang@intel.com \
--cc=zhihong.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.