From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/5] vhost: enable for all targets
Date: Mon, 26 Nov 2018 17:43:28 -0500 [thread overview]
Message-ID: <20181126173604-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1543238443-4993-1-git-send-email-pbonzini@redhat.com>
On Mon, Nov 26, 2018 at 02:20:38PM +0100, Paolo Bonzini wrote:
> vhost does not have to be supported only if KVM is present, in fact
> vhost-user does not even need any kind of kernel support. This series
> changes this. The rationale is that, when vhost-user-test.c will be
> converted to qgraph, it will be able to test vhost-user support
> for virtio-mmio backend even on x86.
The reason for limiting it to KVM was very simple:
it has the same set of problems with ordering
as mttcg.
So I guess it's fine but I think we must then limit it
to when tcg emits fence instructions.
Otherwise we'll get subtle race conditions.
> Paolo Bonzini (5):
> 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-net: compile it on all targets that have virtio-net.
> vhost-net: revamp configure logic
>
> backends/Makefile.objs | 5 +--
> configure | 101 ++++++++++++++++++++++++++++-----------------
> default-configs/virtio.mak | 4 +-
> hw/net/Makefile.objs | 4 +-
> hw/net/vhost_net-stub.c | 95 ++++++++++++++++++++++++++++++++++++++++++
> hw/net/vhost_net.c | 78 ++--------------------------------
> hw/virtio/Makefile.objs | 5 ++-
> hw/virtio/vhost-backend.c | 11 ++++-
> include/exec/poison.h | 1 -
> net/Makefile.objs | 4 +-
> net/net.c | 2 +-
> net/vhost-user-stub.c | 23 +++++++++++
> tests/Makefile.include | 5 +--
> 13 files changed, 209 insertions(+), 129 deletions(-)
> create mode 100644 hw/net/vhost_net-stub.c
> create mode 100644 net/vhost-user-stub.c
>
> --
> 1.8.3.1
next prev parent reply other threads:[~2018-11-26 22:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 13:20 [Qemu-devel] [PATCH 0/5] vhost: enable for all targets Paolo Bonzini
2018-11-26 13:20 ` [Qemu-devel] [PATCH 1/5] vhost-net: move stubs to a separate file Paolo Bonzini
2018-11-26 13:20 ` [Qemu-devel] [PATCH 2/5] vhost-net-user: add stubs for when no virtio-net device is present Paolo Bonzini
2018-11-26 16:45 ` Philippe Mathieu-Daudé
2018-11-26 22:43 ` Michael S. Tsirkin
2018-11-26 22:52 ` Philippe Mathieu-Daudé
2018-11-26 13:20 ` [Qemu-devel] [PATCH 3/5] vhost: restrict Linux dependency to kernel vhost Paolo Bonzini
2018-11-26 16:51 ` Philippe Mathieu-Daudé
2018-11-26 13:20 ` [Qemu-devel] [PATCH 4/5] vhost-net: compile it on all targets that have virtio-net Paolo Bonzini
2018-11-26 16:55 ` Philippe Mathieu-Daudé
2018-11-26 13:20 ` [Qemu-devel] [PATCH 5/5] vhost-net: revamp configure logic Paolo Bonzini
2018-11-26 17:00 ` Philippe Mathieu-Daudé
2018-11-26 22:43 ` Michael S. Tsirkin [this message]
2018-11-27 9:04 ` [Qemu-devel] [PATCH 0/5] vhost: enable for all targets Paolo Bonzini
2018-11-27 16:27 ` Michael S. Tsirkin
2018-11-27 17:00 ` Paolo Bonzini
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=20181126173604-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).