From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Cc: a.motakis@virtualopensystems.com, luke@snabb.co,
snabb-devel@googlegroups.com, qemu-devel@nongnu.org,
tech@virtualopensystems.com
Subject: Re: [Qemu-devel] [PATCH 0/3] Fixups for vhost-user
Date: Fri, 13 Jun 2014 11:04:00 +0300 [thread overview]
Message-ID: <20140613080400.GD2117@redhat.com> (raw)
In-Reply-To: <20140613064414.7683.63231.stgit@3820>
On Fri, Jun 13, 2014 at 09:49:38AM +0300, Nikolay Nikolaev wrote:
> This is a series of fixups that replace 'memory-file' with
> 'memory-backend-file'. This is the object type used in the newest (since v4)
> NUMA series for the file based host memory backend.
>
> The patches are against git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git
> branch 'vhost'. Tested after rebasing on same tree branch 'numa'.
Will apply Sunday.
>From now on pls work on top of the pci branch.
Thanks!
> ---
>
> Nikolay Nikolaev (3):
> fixup! Add vhost-user as a vhost backend.
> fixup! Add the vhost-user netdev backend to the command line
> fixup! Add qtest for vhost-user
>
>
> docs/specs/vhost-user.txt | 266 ++++++++++++++++++++++++++++++++++++++
> hmp-commands.hx | 4 -
> hw/net/vhost_net.c | 39 ++++++
> hw/virtio/vhost-user.c | 2
> include/net/vhost-user.h | 17 ++
> net/Makefile.objs | 2
> net/clients.h | 3
> net/hub.c | 1
> net/net.c | 3
> net/vhost-user.c | 258 +++++++++++++++++++++++++++++++++++++
> qapi-schema.json | 19 +++
> qemu-options.hx | 18 +++
> stubs/Makefile.objs | 8 +
> stubs/bdrv-commit-all.c | 7 +
> stubs/chr-msmouse.c | 7 +
> stubs/get-next-serial.c | 3
> stubs/is-daemonized.c | 7 +
> stubs/machine-init-done.c | 6 +
> stubs/monitor-init.c | 6 +
> stubs/notify-event.c | 6 +
> stubs/vc-init.c | 7 +
> tests/Makefile | 4 +
> tests/vhost-user-test.c | 312 +++++++++++++++++++++++++++++++++++++++++++++
> 23 files changed, 1000 insertions(+), 5 deletions(-)
> create mode 100644 docs/specs/vhost-user.txt
> create mode 100644 include/net/vhost-user.h
> create mode 100644 net/vhost-user.c
> create mode 100644 stubs/bdrv-commit-all.c
> create mode 100644 stubs/chr-msmouse.c
> create mode 100644 stubs/get-next-serial.c
> create mode 100644 stubs/is-daemonized.c
> create mode 100644 stubs/machine-init-done.c
> create mode 100644 stubs/monitor-init.c
> create mode 100644 stubs/notify-event.c
> create mode 100644 stubs/vc-init.c
> create mode 100644 tests/vhost-user-test.c
>
> --
> Signature
next prev parent reply other threads:[~2014-06-13 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 6:49 [Qemu-devel] [PATCH 0/3] Fixups for vhost-user Nikolay Nikolaev
2014-06-13 6:49 ` [Qemu-devel] [PATCH 1/3] fixup! Add vhost-user as a vhost backend Nikolay Nikolaev
2014-06-13 6:50 ` [Qemu-devel] [PATCH 2/3] fixup! Add the vhost-user netdev backend to the command line Nikolay Nikolaev
2014-06-13 6:50 ` [Qemu-devel] [PATCH 3/3] fixup! Add qtest for vhost-user Nikolay Nikolaev
2014-06-13 8:04 ` Michael S. Tsirkin [this message]
2014-06-18 19:15 ` [Qemu-devel] [PATCH 0/3] Fixups " Michael S. Tsirkin
2014-06-18 19:16 ` 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=20140613080400.GD2117@redhat.com \
--to=mst@redhat.com \
--cc=a.motakis@virtualopensystems.com \
--cc=luke@snabb.co \
--cc=n.nikolaev@virtualopensystems.com \
--cc=qemu-devel@nongnu.org \
--cc=snabb-devel@googlegroups.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).