From: Stefan Hajnoczi <stefanha@gmail.com>
To: Antonios Motakis <a.motakis@virtualopensystems.com>
Cc: tech@virtualopensystems.com,
Anthony Liguori <aliguori@amazon.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>,
Markus Armbruster <armbru@redhat.com>,
n.nikolaev@virtualopensystems.com, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>,
lukego@gmail.com, Paolo Bonzini <pbonzini@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/5] Add vhostsock option
Date: Wed, 4 Dec 2013 14:42:15 +0100 [thread overview]
Message-ID: <20131204134215.GA27381@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1385754746-21172-4-git-send-email-a.motakis@virtualopensystems.com>
On Fri, Nov 29, 2013 at 08:52:24PM +0100, Antonios Motakis wrote:
> @@ -91,15 +91,27 @@ static int vhost_net_get_fd(NetClientState *backend)
> }
> }
>
> -struct vhost_net *vhost_net_init(NetClientState *backend, int devfd,
> - bool force)
> +struct vhost_net *vhost_net_init(NetClientState *backend, char *vhostsock,
> + int devfd, bool force)
> {
> int r;
> struct vhost_net *net = g_malloc(sizeof *net);
> + const char *backend_sock = 0;
> + VhostBackendType backend_type = VHOST_BACKEND_TYPE_NONE;
> +
> if (!backend) {
> fprintf(stderr, "vhost-net requires backend to be setup\n");
> goto fail;
> }
> +
> + if (vhostsock && strcmp(vhostsock, VHOST_NET_DEFAULT_SOCK) != 0) {
This is a weird hack. Why check for VHOST_NET_DEFAULT_SOCK at all?
If the option is not present then kernel vhost is used, if the option is
present then userspace vhost is used. I don't understand why a magic
hardcoded path is useful.
next prev parent reply other threads:[~2013-12-04 13:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 19:52 [Qemu-devel] [RFC 0/5] Vhost and vhost-net support for userspace based backends Antonios Motakis
2013-11-29 19:52 ` [Qemu-devel] [PATCH 1/5] Decouple vhost from kernel interface Antonios Motakis
2013-11-29 19:52 ` [Qemu-devel] [PATCH 2/5] Add vhost-kernel and the vhost-user skeleton Antonios Motakis
2013-12-04 13:47 ` Stefan Hajnoczi
2013-12-04 15:23 ` Antonios Motakis
2013-11-29 19:52 ` [Qemu-devel] [PATCH 3/5] Add vhostsock option Antonios Motakis
2013-12-04 13:42 ` Stefan Hajnoczi [this message]
2013-12-04 15:21 ` Antonios Motakis
2013-12-04 14:28 ` Eric Blake
2013-11-29 19:52 ` [Qemu-devel] [PATCH 4/5] Add domain socket communication for vhost-user backend Antonios Motakis
2013-11-29 19:52 ` [Qemu-devel] [PATCH 5/5] Add vhost-user calls implementation Antonios Motakis
2013-12-04 20:00 ` Michael S. Tsirkin
2013-12-10 12:05 ` Antonios Motakis
2013-12-04 13:56 ` [Qemu-devel] [RFC 0/5] Vhost and vhost-net support for userspace based backends Stefan Hajnoczi
2013-12-04 15:23 ` Antonios Motakis
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=20131204134215.GA27381@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=a.motakis@virtualopensystems.com \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lukego@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=n.nikolaev@virtualopensystems.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=tech@virtualopensystems.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).