From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: dev@dpdk.org, ann.zhuangyanying@huawei.com
Subject: Re: [dpdk-dev] [PATCH v2] vhost: Fix reset_owner message handling not to clear callfd
Date: Tue, 24 Nov 2015 13:42:49 +0900 [thread overview]
Message-ID: <5653EAC9.80704@igel.co.jp> (raw)
In-Reply-To: <20151120112125.GA2325@yliu-dev.sh.intel.com>
On 2015/11/20 20:21, Yuanhan Liu wrote:
> On Thu, Nov 19, 2015 at 06:07:00PM +0900, Tetsuya Mukawa wrote:
>> The patch fixes reset_owner message handling not to clear callfd,
>> because callfd will be valid while connection is establihed.
>>
>> Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp>
> ....
>>
>> /*
>> @@ -467,6 +486,7 @@ static int
>> reset_owner(struct vhost_device_ctx ctx)
>> {
>> struct virtio_net *dev;
>> + uint32_t i;
>>
>> dev = get_device(ctx);
>> if (dev == NULL)
>> @@ -475,7 +495,19 @@ reset_owner(struct vhost_device_ctx ctx)
>> if (dev->flags & VIRTIO_DEV_RUNNING)
>> notify_destroy_device(dev);
>>
>> - cleanup_device(dev);
> I would suggest to introduce the destory flag to cleanup_device() as
> well, so that we don't have to unfold the cleanup_device code here.
>
> (BTW, I should've reviewed this patch this morning, but I was busy).
Thanks, I will submit it again.
Tetsuya
next prev parent reply other threads:[~2015-11-24 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 6:23 [dpdk-dev] [PATCH] " Tetsuya Mukawa
2015-11-19 7:03 ` Yuanhan Liu
2015-11-19 7:12 ` Tetsuya Mukawa
2015-11-19 9:07 ` [dpdk-dev] [PATCH v2] " Tetsuya Mukawa
2015-11-20 11:21 ` Yuanhan Liu
2015-11-24 4:42 ` Tetsuya Mukawa [this message]
2015-11-24 6:45 ` [dpdk-dev] [PATCH v3] " Tetsuya Mukawa
2015-11-24 7:15 ` Yuanhan Liu
2015-11-24 19:04 ` Thomas Monjalon
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=5653EAC9.80704@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=ann.zhuangyanying@huawei.com \
--cc=dev@dpdk.org \
--cc=yuanhan.liu@linux.intel.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).