On Sat, 12 Nov 2016 00:03:14 +0100
Paolo Bonzini wrote:
> On 11/11/2016 22:11, Alex Williamson wrote:
> > On Fri, 11 Nov 2016 20:46:53 +
> > Felipe Franciosi wrote:
> >
> >> The trace you showed is exactly the same I encountered on vhost-scsi. And
> >> the one my (hacky) patched fixed. T
On 11/11/2016 22:11, Alex Williamson wrote:
> On Fri, 11 Nov 2016 20:46:53 +
> Felipe Franciosi wrote:
>
>> The trace you showed is exactly the same I encountered on vhost-scsi. And
>> the one my (hacky) patched fixed. The summary of my investigation is on the
>> patch description. I'm OO
On Fri, 11 Nov 2016 20:46:53 +
Felipe Franciosi wrote:
> The trace you showed is exactly the same I encountered on vhost-scsi. And the
> one my (hacky) patched fixed. The summary of my investigation is on the patch
> description. I'm OOO so apologies for not being of more help. F.
Paolo's
The trace you showed is exactly the same I encountered on vhost-scsi. And the
one my (hacky) patched fixed. The summary of my investigation is on the patch
description. I'm OOO so apologies for not being of more help. F.
Sent from my phone
> On 11 Nov 2016, at 20:38, Alex Williamson wrote:
>
On Fri, 11 Nov 2016 20:28:55 +0100
Paolo Bonzini wrote:
> Following the recent refactoring of virtio notifiers [1], more specifically
> the patch ed08a2a0b ("virtio: use virtio_bus_set_host_notifier to
> start/stop ioeventfd") that uses virtio_bus_set_host_notifier [2]
> by default, core virtio c
Following the recent refactoring of virtio notifiers [1], more specifically
the patch ed08a2a0b ("virtio: use virtio_bus_set_host_notifier to
start/stop ioeventfd") that uses virtio_bus_set_host_notifier [2]
by default, core virtio code requires 'ioeventfd_started' to be set
to true/false when the
