On 30/03/2016 05:04, tu bo wrote:
> Hi Christian:
>
> On 03/30/2016 12:31 AM, Christian Borntraeger wrote:
>> On 03/29/2016 03:42 PM, Michael S. Tsirkin wrote:
>>> This works around races that data plane introduces
>>> simply by exiting immediately if we detect
>>> that dataplane is active.
>>>
Hi Christian:
On 03/30/2016 12:31 AM, Christian Borntraeger wrote:
On 03/29/2016 03:42 PM, Michael S. Tsirkin wrote:
This works around races that data plane introduces
simply by exiting immediately if we detect
that dataplane is active.
It's a small but ugly patch, it's only justification
is t
On 03/29/2016 03:42 PM, Michael S. Tsirkin wrote:
> This works around races that data plane introduces
> simply by exiting immediately if we detect
> that dataplane is active.
>
> It's a small but ugly patch, it's only justification
> is that it's minimally intrusive, and that it clearly
> has no
On Tue, 29 Mar 2016 16:42:09 +0300
"Michael S. Tsirkin" wrote:
> This works around races that data plane introduces
> simply by exiting immediately if we detect
> that dataplane is active.
>
> It's a small but ugly patch, it's only justification
> is that it's minimally intrusive, and that it cl
On Tue, Mar 29, 2016 at 04:42:09PM +0300, Michael S. Tsirkin wrote:
> This works around races that data plane introduces
> simply by exiting immediately if we detect
> that dataplane is active.
>
> It's a small but ugly patch, it's only justification
> is that it's minimally intrusive, and that it
This works around races that data plane introduces
simply by exiting immediately if we detect
that dataplane is active.
It's a small but ugly patch, it's only justification
is that it's minimally intrusive, and that it clearly
has no chance to break non data plane users.
The idea is to rework it
