qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] 答复: Re: [PATCH] vhost: don't set vring call fd to -1 i


From: Jason Wang
Subject: Re: [Qemu-devel] 答复: Re: [PATCH] vhost: don't set vring call fd to -1 invhost_virtqueue_start for vhost-user
Date: Mon, 21 Aug 2017 11:34:48 +0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1



On 2017年08月21日 11:28, address@hidden wrote:
  if (!vdev->use_guest_notifier_mask) {

         /* TODO: check and handle errors. */

         vhost_virtqueue_mask(dev, vdev, idx, false)

         ---------- set right  callfd

     }




     if (k->query_guest_notifiers &&

         k->query_guest_notifiers(qbus->parent) &&

         virtio_queue_vector(vdev, idx) == VIRTIO_NO_VECTOR) {

         file.fd = -1

         r = dev->vhost_ops->vhost_set_vring_call(dev, &file)

-----------set call fd to -1

         if (r) {

             goto fail_vector

         }

     }

  So   the callfd of  ovs+dpdk in host  is -1.  it  can't be able  to interact 
with the guest.



The queue does not even an vector, so it won't generate any interrupt. Why callfd is still needed?

Thanks




reply via email to

[Prev in Thread] Current Thread [Next in Thread]