From: "zhengxiang (A)" <zhengxiang9@huawei.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Laszlo Ersek <lersek@redhat.com>
Cc: <edk2-devel@lists.01.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jordan Justen <jordan.l.justen@intel.com>,
Shannon Zhao <zhaoshenglong@huawei.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH] OvmfPkg/VirtioScsiDxe: Allocate all required vrings at VirtioScsiInit
Date: Thu, 14 Dec 2017 21:25:32 +0800 [thread overview]
Message-ID: <835f9103-1892-4963-9bbb-1fa9b417af60@huawei.com> (raw)
In-Reply-To: <b3d836e1-8e64-da5e-4510-cb1b57efcd03@redhat.com>
On 2017/12/14 17:06, Paolo Bonzini wrote:
> On 14/12/2017 07:55, zhengxiang (A) wrote:
>> Hello Laszlo and Paolo,
>>
>> Thanks for your review!
>>
>> On 2017/12/13 19:16, Laszlo Ersek wrote:
>>> On 12/13/17 10:29, Paolo Bonzini wrote:
>>>> On 13/12/2017 09:35, Laszlo Ersek wrote:
>>>>> Perhaps you can update vhost-scsi similarly to the last patch of
>>>>> Maxime's v4 series, even without "VIRTIO_SCSI_F_MQ" -- in the
>>>>> SET_FEATURES request handler, just destroy the unused virtqueues that
>>>>> have not been configured by the guest driver until that time?
>>>> Yes, this is the right solution. We can assume that if the descriptor
>>>> address is equal to zero, the queue is not in use. This is not in the
>>>> spec as far as I can see, but it is QEMU's assumption. I will send a
>>>> patch to the virtio specification.
>>
>> I would try this solution! However, is there any possibility that the allocated
>> descriptor address is exactly equal to zero and the queue is in use?
>
> That would break QEMU's virtio implementation, so it's pretty unlikely.
>
> Paolo
>
So could I judge the not-in-use queues by adding the below sentence in order
to skip calling vhost_virtqueue_start?
diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
index e4290ce..05c3322 100644
--- a/hw/virtio/vhost.c
+++ b/hw/virtio/vhost.c
@@ -1532,6 +1532,7 @@ int vhost_dev_start(struct vhost_dev *hdev, VirtIODevice *vdev)
goto fail_mem;
}
for (i = 0; i < hdev->nvqs; ++i) {
+ if (virtio_queue_get_desc_addr(vdev, i) == 0) continue;
r = vhost_virtqueue_start(hdev,
vdev,
hdev->vqs + i,
Thanks,
Xiang
next prev parent reply other threads:[~2017-12-14 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 3:16 [PATCH] OvmfPkg/VirtioScsiDxe: Allocate all required vrings at VirtioScsiInit Zheng Xiang
2017-12-13 8:35 ` Laszlo Ersek
2017-12-13 9:29 ` Paolo Bonzini
2017-12-13 11:04 ` Laszlo Ersek
2017-12-13 11:16 ` Laszlo Ersek
2017-12-14 6:55 ` zhengxiang (A)
2017-12-14 9:06 ` Paolo Bonzini
2017-12-14 13:25 ` zhengxiang (A) [this message]
2018-01-11 13:23 ` Maxime Coquelin
2018-01-11 14:46 ` Maxime Coquelin
2018-01-12 1:35 ` zhengxiang (A)
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-list 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=835f9103-1892-4963-9bbb-1fa9b417af60@huawei.com \
--to=devel@edk2.groups.io \
/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