From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Zhoujian (jay)" <jianjay.zhou@huawei.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Huangweidong (C)" <weidong.huang@huawei.com>,
"wangxin (U)" <wangxinxin.wang@huawei.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
"Liuzhe (Ahriy, Euler)" <liuzhe13@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v5 0/4] vhost: two fixes and used_memslots refactoring
Date: Thu, 11 Jan 2018 21:55:52 +0200 [thread overview]
Message-ID: <20180111215411-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <B2D15215269B544CADD246097EACE7473AB386CE@DGGEMM505-MBS.china.huawei.com>
On Thu, Jan 11, 2018 at 01:55:38PM +0000, Zhoujian (jay) wrote:
> Hi Igor,
>
> > -----Original Message-----
> > From: Igor Mammedov [mailto:imammedo@redhat.com]
> > Sent: Thursday, January 11, 2018 9:05 PM
> > To: Zhoujian (jay) <jianjay.zhou@huawei.com>
> > Cc: qemu-devel@nongnu.org; mst@redhat.com; Huangweidong (C)
> > <weidong.huang@huawei.com>; wangxin (U) <wangxinxin.wang@huawei.com>; Gonglei
> > (Arei) <arei.gonglei@huawei.com>; Liuzhe (Ahriy, Euler) <liuzhe13@huawei.com>
> > Subject: Re: [PATCH v5 0/4] vhost: two fixes and used_memslots refactoring
> >
> > 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.
>
> Will look into the testcases. Maybe it would take some time since I'm not
> very familiar with them.
>
> Regards,
> Jay
ok can you repost whatever's ready please? And please use proper
threading (e.g. generated with git format-patch --thread=shallow).
> >
> > > 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
> > >
> > >
next prev parent reply other threads:[~2018-01-11 19:56 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 [this message]
2018-01-12 1:41 ` Zhoujian (jay)
2018-01-11 20:13 ` Michael S. Tsirkin
2018-01-12 9:18 ` Igor Mammedov
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=20180111215411-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=imammedo@redhat.com \
--cc=jianjay.zhou@huawei.com \
--cc=liuzhe13@huawei.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).