qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: qemu-devel@nongnu.org
Cc: marcel@redhat.com, jasowang@redhat.com, famz@redhat.com, mst@redhat.com
Subject: [Qemu-devel]  [PATCH V2 0/2] vhost-user: sync backend
Date: Wed, 29 Jul 2015 23:06:47 +0300	[thread overview]
Message-ID: <1438200409-27381-1-git-send-email-marcel@redhat.com> (raw)

 To be used on top of:
 [PATCH 0/4] vhost-user: protocol updates
 https://lists.gnu.org/archive/html/qemu-devel/2015-07/msg03842.html 

 v1 -> v2:
 - Addressed Michael S. Tsirkin's comments:
   - Prefer a white-list of supported features
   - Add a unit-test to show the problem we are trying to solve
     (run the unit-test before the patch and it will fail)

 Currently the vhost-user supported features are not evaluated.
 The way I see it, and please correct me, the best way to do
 this is to:
  1. Get the backend features on vhost init.
  2. Check them one by one (white-list) against all 
     the currently supported virtio features.
  3. All other code should remain the same.

Marcel Apfelbaum (2):
  vhost-user: sync backend features
  tests/vhost-user: check vhost-user feature negotiation

 hw/virtio/vhost-user.c  | 17 +++++++++++++++++
 tests/vhost-user-test.c | 19 ++++++++++++++++---
 2 files changed, 33 insertions(+), 3 deletions(-)

-- 
2.1.0

             reply	other threads:[~2015-07-29 20:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 20:06 Marcel Apfelbaum [this message]
2015-07-29 20:06 ` [Qemu-devel] [PATCH V2 1/2] vhost-user: sync backend features Marcel Apfelbaum
2015-07-30  6:47   ` Michael S. Tsirkin
2015-07-30  7:27     ` Marcel Apfelbaum
2015-07-29 20:06 ` [Qemu-devel] [PATCH V2 2/2] tests/vhost-user: check vhost-user feature negotiation Marcel Apfelbaum
2015-07-30  6:47   ` Michael S. Tsirkin
2015-07-30  7:30     ` Marcel Apfelbaum

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=1438200409-27381-1-git-send-email-marcel@redhat.com \
    --to=marcel@redhat.com \
    --cc=famz@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@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).