qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Tetsuya Mukawa <mukawa@igel.co.jp>
Cc: jasowang@redhat.com, qemu-devel@nongnu.org,
	n.nikolaev@virtualopensystems.com,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 0/4] Add feature to start QEMU without vhost-user backend
Date: Mon, 15 Jun 2015 15:12:28 +0100	[thread overview]
Message-ID: <20150615141228.GG9410@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <5578EAB6.9070409@igel.co.jp>

[-- Attachment #1: Type: text/plain, Size: 4331 bytes --]

On Thu, Jun 11, 2015 at 10:56:06AM +0900, Tetsuya Mukawa wrote:
> On 2015/05/29 13:42, Tetsuya Mukawa wrote:
> > Hi guys,
> >
> > Here are patches to add feature to start QEMU without vhost-user backend.
> > Currently, if we want to use vhost-user backend, the backend must start before
> > QEMU. Also, if QEMU or the backend is closed unexpectedly, there is no way to
> > recover without restarting both applications. Practically, it's not useful.
> >
> > This patch series adds following features.
> >  - QEMU can start before the backend.
> >  - QEMU or the backend can restart anytime.
> >    connectivity will be recovered automatically, when app starts again.
> >    (if QEMU is server, QEMU just wait reconnection)
> >    while lost connection, link status of virtio-net device is down,
> >    so virtio-net driver on the guest can know it
> >
> > To work like above, the patch introduces flags to specify features vhost-user
> > backend will support.
> >
> > Here are examples.
> > ('backend_mrg_rxbuf' is an one of new flags. To know all, check the last patch)
> >
> >     * QEMU is configured as vhost-user client.
> >      -chardev socket,id=chr0,path=/tmp/sock,reconnect=3 \
> >      -netdev vhost-user,id=net0,chardev=chr0,vhostforce,backend_mrg_rxbuf \
> >      -device virtio-net-pci,netdev=net0 \
> >
> >     * QEMU is configured as vhost-user server.
> >      -chardev socket,id=chr0,path=/tmp/sock,server,nowait \
> >      -netdev vhost-user,id=net0,chardev=chr0,vhostforce,backend_mrg_rxbuf \
> >      -device virtio-net-pci,netdev=net0 \
> >
> > When virtio-net device is configured by virtio-net driver, QEMU should know
> > vhost-user backend features. But if QEMU starts without the backend, QEMU cannot
> > know it. So above the feature values specified by user will be used as features
> > the backend will support.
> >
> > When connection between QEMU and the backend is established, QEMU checkes feature
> > values of the backend to make sure the expected features are provided.
> > If it doesn't, the connection will be closed by QEMU.
> >
> > Regards,
> > Tetsuya
> >
> > ----------
> > Changes
> > ----------
> > - Changes from RFC patch
> >   The last patch of this series was changed like below.
> >    - Rebase to latest master.
> >    - Remove needless has_backend_feature variable.
> >    - Change user interface to be able to specify each feature by name.
> >    - Add (Since 2.4) to schema file.
> >    - Fix commit title and body.
> >
> >
> > Tetsuya Mukawa (4):
> >   vhost-user: Add ability to know vhost-user backend disconnection
> >   vhost-user: Shutdown vhost-user connection when wrong messages are
> >     passed
> >   vhost-user: Enable 'nowait' and 'reconnect' option
> >   vhost-user: Add new option to specify vhost-user backend features
> >
> >  hw/net/vhost_net.c             |   6 ++-
> >  hw/net/virtio-net.c            |  13 +++++
> >  hw/scsi/vhost-scsi.c           |   2 +-
> >  hw/virtio/vhost-user.c         |  24 ++++++---
> >  hw/virtio/vhost.c              |   7 ++-
> >  include/hw/virtio/vhost.h      |   3 +-
> >  include/hw/virtio/virtio-net.h |   1 +
> >  include/net/net.h              |   3 ++
> >  include/net/vhost_net.h        |   1 +
> >  include/sysemu/char.h          |   7 +++
> >  net/net.c                      |   9 ++++
> >  net/tap.c                      |   1 +
> >  net/vhost-user.c               |  69 ++++++++++++++++++++++++-
> >  qapi-schema.json               | 114 +++++++++++++++++++++++++++++++++++------
> >  qemu-char.c                    |  15 ++++++
> >  qemu-options.hx                |  10 ++++
> >  16 files changed, 256 insertions(+), 29 deletions(-)
> >
> 
> Ping.
> 
> Could someone please review this patches?
> http://patchwork.ozlabs.org/project/qemu-devel/list/?submitter=66139

Nikolay, Jason, or Michael:
Can one of you please step up to become maintainer of net/vhost-user.c.

I don't follow vhost-user development much and can't give good review
feedback about the vhost-user specific aspects.

Please send a patch that adds you to the MAINTAINERS file for
net/vhost-user.c.  Then either include merged patches in Michael's pull
requests or ask me (and in the future, Jason) to include them in net
pull requests.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-06-15 14:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25  7:28 [Qemu-devel] [RFC PATCH 0/4] Add feature to start QEMU without vhost-user backend Tetsuya Mukawa
2015-05-25  7:28 ` [Qemu-devel] [RFC PATCH 1/4] vhost-user: Add ability to know vhost-user backend disconnection Tetsuya Mukawa
2015-05-25  7:28 ` [Qemu-devel] [RFC PATCH 2/4] vhost-user: Shutdown vhost-user connection when wrong messages are passed Tetsuya Mukawa
2015-05-25  7:28 ` [Qemu-devel] [RFC PATCH 3/4] vhost-user: Enable 'nowait' and 'reconnect' option Tetsuya Mukawa
2015-05-25  7:28 ` [Qemu-devel] [RFC PATCH 4/4] vhost-user: Add new option to specify vhost-user backend supports Tetsuya Mukawa
2015-05-25 22:11   ` Eric Blake
2015-05-26  2:46     ` Tetsuya Mukawa
2015-05-26  4:29       ` Tetsuya Mukawa
2015-05-26 12:52         ` Eric Blake
2015-05-28  1:25           ` Tetsuya Mukawa
2015-05-29  4:42             ` Tetsuya Mukawa
2015-05-29  4:42   ` [Qemu-devel] [PATCH v1 0/4] Add feature to start QEMU without vhost-user backend Tetsuya Mukawa
2015-05-29  4:42     ` [Qemu-devel] [PATCH v1 1/4] vhost-user: Add ability to know vhost-user backend disconnection Tetsuya Mukawa
2015-06-15 13:32       ` Stefan Hajnoczi
2015-06-16  5:07         ` Tetsuya Mukawa
2015-05-29  4:42     ` [Qemu-devel] [PATCH v1 2/4] vhost-user: Shutdown vhost-user connection when wrong messages are passed Tetsuya Mukawa
2015-06-15 13:40       ` Stefan Hajnoczi
2015-06-16  5:08         ` Tetsuya Mukawa
2015-05-29  4:42     ` [Qemu-devel] [PATCH v1 3/4] vhost-user: Enable 'nowait' and 'reconnect' option Tetsuya Mukawa
2015-06-15 13:41       ` Stefan Hajnoczi
2015-06-15 13:58       ` Stefan Hajnoczi
2015-06-16  5:08         ` Tetsuya Mukawa
2015-05-29  4:42     ` [Qemu-devel] [PATCH v1 4/4] vhost-user: Add new option to specify vhost-user backend features Tetsuya Mukawa
2015-06-15 13:58       ` Stefan Hajnoczi
2015-06-16  5:08         ` Tetsuya Mukawa
2015-06-16 12:27       ` Eric Blake
2015-06-17  9:29         ` Tetsuya Mukawa
2015-06-11  1:56     ` [Qemu-devel] [PATCH v1 0/4] Add feature to start QEMU without vhost-user backend Tetsuya Mukawa
2015-06-15 14:12       ` Stefan Hajnoczi [this message]
2015-06-15 14:21         ` Michael S. Tsirkin
2015-06-15 14:08     ` Stefan Hajnoczi
2015-06-16  5:09       ` Tetsuya Mukawa

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=20150615141228.GG9410@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=mukawa@igel.co.jp \
    --cc=n.nikolaev@virtualopensystems.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).