From: Jason Wang <jasowang@redhat.com>
To: "Longpeng (Mike)" <longpeng2@huawei.com>
Cc: "Huangweidong (C)" <weidong.huang@huawei.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Wangjing (King, Euler)" <king.wang@huawei.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
"Longpeng(Mike)" <longpeng.mike@gmail.com>
Subject: Re: [Qemu-devel] [Question] why need to start all queues in vhost_net_start
Date: Thu, 16 Nov 2017 20:04:34 +0800 [thread overview]
Message-ID: <55f2edb1-1fe3-d03f-7f4f-418a3b15997a@redhat.com> (raw)
In-Reply-To: <5A0D5B1B.3080708@huawei.com>
On 2017年11月16日 17:32, Longpeng (Mike) wrote:
> Hi Jason,
>
> On 2017/11/16 17:13, Jason Wang wrote:
>
>>
>> On 2017年11月16日 17:01, Gonglei (Arei) wrote:
>>> No, Windows guest + vhost-user/DPDK.
>>>
>>> BTW pls see virtio spec in :
>>>
>>> "If VIRTIO_NET_F_MQ is negotiated, each of receiveq1. . .receiveqN that will
>>> be used SHOULD be populated
>>> with receive buffers."
>>>
>>> It is not mandatory that all queues must be initialized.
>> I think not, since it said we should fill receive buffers for each queue which
>> means we should initialize all queues. May Michael can clarify on this.
>>
>
> I think this doesn't matter, but QEMU should consider this scenario...
>
> For example, if one queues isn't initialized (Windows guest), the vring.avail=0,
> so vq->desc_phys=0, then vq->desc='a avail HVA'(which is the start addr of pc.ram).
>
> vq->desc_size = s = l = virtio_queue_get_desc_size(vdev, idx);
> vq->desc_phys = a = virtio_queue_get_desc_addr(vdev, idx);
> vq->desc = vhost_memory_map(dev, a, &l, 0);
> if (!vq->desc || l != s) {
> r = -ENOMEM;
> goto fail_alloc_desc;
> }
> .....
> r = vhost_virtqueue_set_addr(dev, vq, vhost_vq_index, dev->log_enabled);
> if (r < 0) {
> r = -errno;
> goto fail_alloc;
> }
>
> Then the HVA is send to the vhost-user.
>
> I think this is wrong, because the '0' here means guest driver doesn't init this
> queues, it should not be used to calculate the HVA for this vq.
Yes, workaround is not hard if windows driver won't use the left 3
queues any more. But we should have a complete solution. The main
problem is when vhost need to be started. For legacy device, there's no
easy way to detect whether or not a specific virtqueue is ready to be
used. For modern device, we can probably do this through queue_enable
(but this is not implemented in current code).
Thanks
>
>> Thanks
>>
>>> Thanks,
>>> -Gonglei
>>>
>>
>>
>>
>> .
>>
>
next prev parent reply other threads:[~2017-11-16 12:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 14:55 [Qemu-devel] [Question] why need to start all queues in vhost_net_start Longpeng(Mike)
2017-11-15 15:05 ` Jason Wang
2017-11-15 15:54 ` Longpeng(Mike)
2017-11-16 5:53 ` Longpeng (Mike)
2017-11-16 8:11 ` Yan Vugenfirer
2017-11-16 11:42 ` Jason Wang
2017-11-16 8:54 ` Jason Wang
2017-11-16 9:01 ` Gonglei (Arei)
2017-11-16 9:09 ` Jason Wang
2017-11-16 9:13 ` Jason Wang
2017-11-16 9:32 ` Longpeng (Mike)
2017-11-16 12:04 ` Jason Wang [this message]
2017-11-17 2:01 ` Longpeng (Mike)
2017-11-17 3:46 ` Jason Wang
2017-11-17 4:32 ` Michael S. Tsirkin
2017-11-17 5:43 ` Longpeng (Mike)
2017-11-17 6:44 ` Jason Wang
2017-11-16 9:08 ` Longpeng (Mike)
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=55f2edb1-1fe3-d03f-7f4f-418a3b15997a@redhat.com \
--to=jasowang@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=king.wang@huawei.com \
--cc=longpeng.mike@gmail.com \
--cc=longpeng2@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).