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] vhost: Fix reset_owner message handling not to clear callfd
Date: Thu, 19 Nov 2015 16:12:11 +0900 [thread overview]
Message-ID: <564D764B.3070003@igel.co.jp> (raw)
In-Reply-To: <20151119070320.GK2326@yliu-dev.sh.intel.com>
On 2015/11/19 16:03, Yuanhan Liu wrote:
> On Thu, Nov 19, 2015 at 03:23:26PM +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>
>> ---
>> lib/librte_vhost/virtio-net.c | 21 ++++++++++++++++++++-
>> 1 file changed, 20 insertions(+), 1 deletion(-)
>>
>> diff --git a/lib/librte_vhost/virtio-net.c b/lib/librte_vhost/virtio-net.c
>> index 886c104..ae1e4bd 100644
>> --- a/lib/librte_vhost/virtio-net.c
>> +++ b/lib/librte_vhost/virtio-net.c
>> @@ -322,6 +322,25 @@ init_vring_queue_pair(struct virtio_net *dev, uint32_t qp_idx)
>> init_vring_queue(dev->virtqueue[base_idx + VIRTIO_TXQ], qp_idx);
>> }
>>
>> +static void
>> +reset_vring_queue(struct vhost_virtqueue *vq, int qp_idx)
>> +{
>> + int callfd;
>> +
>> + callfd = vq->callfd;
>> + init_vring_queue(vq, qp_idx);
>> + vq->callfd = callfd;
> It may fix your issue, but it's not a proper fix. As we actually closed
> callfd at cleanup_vq().
Yes, you are correct.
We also need to fix above.
>
> BTW, the name, cleanup_vq/device, is not well taken. For a name like
> cleanup, those functions should be invoked at device remove stage (say,
> shutting down a VM), but not at reset stage (which is actually treated
> as STOP in current QEMU implementation).
>
> I have a plan to correct it, but I guess it's not the right time as
> v2.2 is coming soon. However, for a fix, it could be simple: how about
> adding another arg to cleanup_vq:
>
> cleanup_vq(struct vhost_virtqueue *vq, int destory)
>
> And we only close callfd when destroy flag is set. (And of course, this
> patch is needed).
Yes I agree with it!
Let me have a few hours, I will send it by today.
Thanks,
Tetsuya
> What do you think of that?
>
> --yliu
>> +}
>> +
>> +static void
>> +reset_vring_queue_pair(struct virtio_net *dev, uint32_t qp_idx)
>> +{
>> + uint32_t base_idx = qp_idx * VIRTIO_QNUM;
>> +
>> + reset_vring_queue(dev->virtqueue[base_idx + VIRTIO_RXQ], qp_idx);
>> + reset_vring_queue(dev->virtqueue[base_idx + VIRTIO_TXQ], qp_idx);
>> +}
>> +
>> static int
>> alloc_vring_queue_pair(struct virtio_net *dev, uint32_t qp_idx)
>> {
>> @@ -362,7 +381,7 @@ reset_device(struct virtio_net *dev)
>> dev->flags = 0;
>>
>> for (i = 0; i < dev->virt_qp_nb; i++)
>> - init_vring_queue_pair(dev, i);
>> + reset_vring_queue_pair(dev, i);
>> }
>>
>> /*
>> --
>> 2.1.4
next prev parent reply other threads:[~2015-11-19 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 6:23 Tetsuya Mukawa
2015-11-19 7:03 ` Yuanhan Liu
2015-11-19 7:12 ` Tetsuya Mukawa [this message]
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
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=564D764B.3070003@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).