On Fri, 1 Apr 2016 15:19:51 +0200
Paolo Bonzini wrote:
> From: "Michael S. Tsirkin"
>
> In addition to handling IO in vcpu thread and in io thread, dataplane
> introduces yet another mode: handling it by aio.
>
> This reuses the same handler as previous modes, which triggers races as
> these
From: "Michael S. Tsirkin"
In addition to handling IO in vcpu thread and in io thread, dataplane
introduces yet another mode: handling it by aio.
This reuses the same handler as previous modes, which triggers races as
these were not designed to be reentrant.
Use a separate handler just for aio,
On 30/03/2016 17:25, Cornelia Huck wrote:
>> >
>> > -/* Some guests kick before setting VIRTIO_CONFIG_S_DRIVER_OK so start
>> > - * dataplane here instead of waiting for .set_status().
>> > - */
>> > -if (s->dataplane && !s->dataplane_started) {
>> > -virtio_blk_data_plan
On Wed, 30 Mar 2016 14:48:05 +0200
Paolo Bonzini wrote:
> From: "Michael S. Tsirkin"
>
> In addition to handling IO in vcpu thread and in io thread, dataplane
> introduces yet another mode: handling it by aio.
>
> This reuses the same handler as previous modes, which triggers races as
> these
From: "Michael S. Tsirkin"
In addition to handling IO in vcpu thread and in io thread, dataplane
introduces yet another mode: handling it by aio.
This reuses the same handler as previous modes, which triggers races as
these were not designed to be reentrant.
Use a separate handler just for aio,
