qemu-arm
[Top][All Lists]
Advanced

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

Re: [Qemu-arm] [PATCH V2] virtio: Fix no interrupt when not creating msi


From: Paolo Bonzini
Subject: Re: [Qemu-arm] [PATCH V2] virtio: Fix no interrupt when not creating msi controller
Date: Mon, 23 Jan 2017 17:46:47 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1


On 23/01/2017 17:07, Michael S. Tsirkin wrote:
> On Mon, Jan 23, 2017 at 08:55:04AM +0800, Shannon Zhao wrote:
>> From: Shannon Zhao <address@hidden>
>>
>> For ARM virt machine, if we use virt-2.7 which will not create ITS node,
>> the virtio-net can not recieve interrupts so it can't get ip address
>> through dhcp.
>> This fixes commit 83d768b(virtio: set ISR on dataplane notifications).
>>
>> Signed-off-by: Shannon Zhao <address@hidden>
> 
> Paolo, could you comment on this pls?

For virtio-blk, my patch moved the setting of ISR from
virtio_queue_guest_notifier_read to virtio_notify_irqfd.  This is
because the irqfd emulation only needs to trigger the interrupt.
Setting the ISR should have been done elsewhere.

Can vhost set ISR (I thought it couldn't)?  If so, it seems like ARM was
relying on QEMU's irqfd emulation, as a work around for vhost not
setting ISR.  But this only works if irqfd is directed to QEMU and not
to KVM.  So if vhost cannot set ISR, I think vhost should be disabled
unless MSI is active.

Am I missing something?

Paolo

> 
>> ---
>> V2: Factor out a common function instead of duplicating code
>> ---
>>  hw/virtio/virtio.c | 11 ++++++++---
>>  1 file changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
>> index aa4f38f..00e8f74 100644
>> --- a/hw/virtio/virtio.c
>> +++ b/hw/virtio/virtio.c
>> @@ -1441,6 +1441,12 @@ void virtio_notify_irqfd(VirtIODevice *vdev, 
>> VirtQueue *vq)
>>      event_notifier_set(&vq->guest_notifier);
>>  }
>>  
>> +static void virtio_irq(VirtQueue *vq)
>> +{
>> +    virtio_set_isr(vq->vdev, 0x1);
>> +    virtio_notify_vector(vq->vdev, vq->vector);
>> +}
>> +
>>  void virtio_notify(VirtIODevice *vdev, VirtQueue *vq)
>>  {
>>      if (!virtio_should_notify(vdev, vq)) {
>> @@ -1448,8 +1454,7 @@ void virtio_notify(VirtIODevice *vdev, VirtQueue *vq)
>>      }
>>  
>>      trace_virtio_notify(vdev, vq);
>> -    virtio_set_isr(vq->vdev, 0x1);
>> -    virtio_notify_vector(vdev, vq->vector);
>> +    virtio_irq(vq);
>>  }
>>  
>>  void virtio_notify_config(VirtIODevice *vdev)
>> @@ -2082,7 +2087,7 @@ static void 
>> virtio_queue_guest_notifier_read(EventNotifier *n)
>>  {
>>      VirtQueue *vq = container_of(n, VirtQueue, guest_notifier);
>>      if (event_notifier_test_and_clear(n)) {
>> -        virtio_notify_vector(vq->vdev, vq->vector);
>> +        virtio_irq(vq);
>>      }
>>  }
>>  
>> -- 
>> 2.0.4
>>



reply via email to

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