From: Igor Mammedov <imammedo@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jay Zhou <jianjay.zhou@huawei.com>,
qemu-devel@nongnu.org, weidong.huang@huawei.com,
wangxinxin.wang@huawei.com, arei.gonglei@huawei.com,
liuzhe13@huawei.com
Subject: Re: [Qemu-devel] [PATCH v5 0/4] vhost: two fixes and used_memslots refactoring
Date: Fri, 12 Jan 2018 10:18:14 +0100 [thread overview]
Message-ID: <20180112101814.44254492@redhat.com> (raw)
In-Reply-To: <20180111221307-mutt-send-email-mst@kernel.org>
On Thu, 11 Jan 2018 22:13:25 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Thu, Jan 11, 2018 at 02:05:20PM +0100, Igor Mammedov wrote:
> > On Wed, 10 Jan 2018 00:39:02 +0800
> > Jay Zhou <jianjay.zhou@huawei.com> wrote:
> >
> > Jay,
> > considering how non trivial touched code is, would you mind
> > first adding 'make check' testcases for success/failure paths
> > that you are touching?
> > It would help with merging and ensure that future changes to
> > vhost won't break memslots handling.
>
> Which tests would you like this to be added to?
At least a test for, so it won't regress unnoticed in future
1st: [PATCH v5 3/4] vhost: fix memslot limit check
2nd: limit check failure triggered when DIMM module hotplugged
PS:
It's fine if tests will be another series on top of this one.
>
> > > v4 -> v5:
> > > Making the followed up device_add to fall back to userspace
> > > virtio when netdev_add fails if vhost force flag does not set.
> > >
> > > Jay Zhou (4):
> > > vhost: remove assertion to prevent crash
> > > tap: do not close fd if only vhost failed to initialize
> > > vhost: fix memslot limit check
> > > vhost: used_memslots refactoring
> > >
> > > hw/virtio/vhost-backend.c | 15 +++++++-
> > > hw/virtio/vhost-user.c | 74 +++++++++++++++++++++++++++------------
> > > hw/virtio/vhost.c | 30 +++++++++-------
> > > include/hw/virtio/vhost-backend.h | 6 ++--
> > > net/tap.c | 25 +++++++++----
> > > 5 files changed, 104 insertions(+), 46 deletions(-)
> > >
> > > --
> > > 1.8.3.1
> > >
> > >
prev parent reply other threads:[~2018-01-12 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 16:39 [Qemu-devel] [PATCH v5 0/4] vhost: two fixes and used_memslots refactoring Jay Zhou
2018-01-11 13:05 ` Igor Mammedov
2018-01-11 13:55 ` Zhoujian (jay)
2018-01-11 19:55 ` Michael S. Tsirkin
2018-01-12 1:41 ` Zhoujian (jay)
2018-01-11 20:13 ` Michael S. Tsirkin
2018-01-12 9:18 ` Igor Mammedov [this message]
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=20180112101814.44254492@redhat.com \
--to=imammedo@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=jianjay.zhou@huawei.com \
--cc=liuzhe13@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.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).