From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/9] vhost: enable for all targets
Date: Thu, 14 Feb 2019 18:35:47 +0100 [thread overview]
Message-ID: <1550165756-21617-1-git-send-email-pbonzini@redhat.com> (raw)
See also "[PATCH for-3.2 00/10] vhost: preparation for qgraph
conversion of vhost-user-test". Some of the other vhost-user-test
patches have gone in already, and this is what is left.
These patches are a prerequisite for both kconfig and qgraph.
I will probably test them on macOS myself before these are included
in a pull request, since the previous versions had some issues.
Michael, let me know if you want me to send the pull request.
Thanks,
Paolo
Paolo Bonzini (9):
vhost-net: move stubs to a separate file
vhost-net-user: add stubs for when no virtio-net device is present
vhost: restrict Linux dependency to kernel vhost
vhost-user: support cross-endian vnet headers
vhost-net: compile it on all targets that have virtio-net.
vhost-net: revamp configure logic
vhost-user-test: create a main loop per TestServer
vhost-user-test: small changes to init_hugepagefs
vhost-user-test: create a temporary directory per TestServer
backends/Makefile.objs | 5 +-
configure | 102 ++++++++++++++++++-----------
default-configs/virtio.mak | 4 +-
hw/net/Makefile.objs | 4 +-
hw/net/vhost_net-stub.c | 92 ++++++++++++++++++++++++++
hw/net/vhost_net.c | 85 ++----------------------
hw/virtio/Makefile.objs | 8 ++-
hw/virtio/vhost-backend.c | 12 +++-
hw/virtio/vhost-user.c | 13 +++-
hw/virtio/vhost.c | 2 +-
include/exec/poison.h | 1 -
net/Makefile.objs | 4 +-
net/net.c | 2 +-
net/vhost-user-stub.c | 23 +++++++
net/vhost-user.c | 13 ++++
tests/Makefile.include | 5 +-
tests/vhost-user-test.c | 160 +++++++++++++++++++++++----------------------
17 files changed, 319 insertions(+), 216 deletions(-)
create mode 100644 hw/net/vhost_net-stub.c
create mode 100644 net/vhost-user-stub.c
--
1.8.3.1
next reply other threads:[~2019-02-14 17:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 17:35 Paolo Bonzini [this message]
2019-02-14 17:35 ` [Qemu-devel] [PATCH 1/9] vhost-net: move stubs to a separate file Paolo Bonzini
2019-02-14 17:35 ` [Qemu-devel] [PATCH 2/9] vhost-net-user: add stubs for when no virtio-net device is present Paolo Bonzini
2019-02-14 17:35 ` [Qemu-devel] [PATCH 3/9] vhost: restrict Linux dependency to kernel vhost Paolo Bonzini
2019-02-14 17:35 ` [Qemu-devel] [PATCH 4/9] vhost-user: support cross-endian vnet headers Paolo Bonzini
2019-02-14 17:35 ` [Qemu-devel] [PATCH 5/9] vhost-net: compile it on all targets that have virtio-net Paolo Bonzini
2019-02-14 17:35 ` [Qemu-devel] [PATCH 6/9] vhost-net: revamp configure logic Paolo Bonzini
2019-02-14 17:35 ` [Qemu-devel] [PATCH 7/9] vhost-user-test: create a main loop per TestServer Paolo Bonzini
2019-02-14 17:35 ` [Qemu-devel] [PATCH 8/9] vhost-user-test: small changes to init_hugepagefs Paolo Bonzini
2019-02-15 8:27 ` Thomas Huth
2019-02-14 17:35 ` [Qemu-devel] [PATCH 9/9] vhost-user-test: create a temporary directory per TestServer Paolo Bonzini
2019-02-14 19:05 ` [Qemu-devel] [PATCH v2 0/9] vhost: enable for all targets Michael S. Tsirkin
2019-02-14 19:28 ` Michael S. Tsirkin
2019-02-14 20:37 ` Paolo Bonzini
2019-02-15 4:25 ` Michael S. Tsirkin
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=1550165756-21617-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).