Re: [dpdk-dev] [PATCH 1/3] net/virtio-user: fix deadlock in memory events callback

2018-09-11 Thread Maxime Coquelin
On 09/05/2018 06:28 AM, Tiwei Bie wrote: Deadlock can occur when allocating memory if a vhost-kernel based virtio-user device is in use. To fix the deadlock, we will take memory hotplug lock explicitly in virtio-user when necessary, and always call the _thread_unsafe memory functions. Bugzill

Re: [dpdk-dev] [PATCH 1/3] net/virtio-user: fix deadlock in memory events callback

2018-09-07 Thread Burakov, Anatoly
On 05-Sep-18 5:28 AM, Tiwei Bie wrote: Deadlock can occur when allocating memory if a vhost-kernel based virtio-user device is in use. To fix the deadlock, we will take memory hotplug lock explicitly in virtio-user when necessary, and always call the _thread_unsafe memory functions. Bugzilla ID:

Re: [dpdk-dev] [PATCH 1/3] net/virtio-user: fix deadlock in memory events callback

2018-09-05 Thread Sean Harte
On 5 September 2018 at 05:28, Tiwei Bie wrote: > Deadlock can occur when allocating memory if a vhost-kernel > based virtio-user device is in use. To fix the deadlock, > we will take memory hotplug lock explicitly in virtio-user > when necessary, and always call the _thread_unsafe memory > functio

[dpdk-dev] [PATCH 1/3] net/virtio-user: fix deadlock in memory events callback

2018-09-04 Thread Tiwei Bie
Deadlock can occur when allocating memory if a vhost-kernel based virtio-user device is in use. To fix the deadlock, we will take memory hotplug lock explicitly in virtio-user when necessary, and always call the _thread_unsafe memory functions. Bugzilla ID: 81 Fixes: 12ecb2f63b12 ("net/virtio-user