Re: [dpdk-dev] [PATCH v3] vhost_user: protect active rings from async ring changes

2017-12-14 Thread Maxime Coquelin
On 12/14/2017 03:21 PM, Victor Kaplansky wrote: - Original Message - From: "Maxime Coquelin" To: "Victor Kaplansky" , dev@dpdk.org Cc: sta...@dpdk.org, "Jens Freimann" , "Yuanhan Liu" , "Tiwei Bie" , "Jianfeng Tan" Sent: Thursday, December 14, 2017 2:16:23 PM Subject: Re: [PATCH v

Re: [dpdk-dev] [PATCH v3] vhost_user: protect active rings from async ring changes

2017-12-14 Thread Victor Kaplansky
- Original Message - > From: "Maxime Coquelin" > To: "Victor Kaplansky" , dev@dpdk.org > Cc: sta...@dpdk.org, "Jens Freimann" , "Yuanhan Liu" > , "Tiwei Bie" > , "Jianfeng Tan" > Sent: Thursday, December 14, 2017 2:16:23 PM > Subject: Re: [PATCH v3] vhost_user: protect active rings fro

Re: [dpdk-dev] [PATCH v3] vhost_user: protect active rings from async ring changes

2017-12-14 Thread Maxime Coquelin
Hi Victor, On 12/14/2017 12:35 PM, Victor Kaplansky wrote: When performing live migration or memory hot-plugging, the changes to the device and vrings made by message handler done independently from vring usage by PMD threads. This causes for example segfaults during live-migration with MQ enab

[dpdk-dev] [PATCH v3] vhost_user: protect active rings from async ring changes

2017-12-14 Thread Victor Kaplansky
When performing live migration or memory hot-plugging, the changes to the device and vrings made by message handler done independently from vring usage by PMD threads. This causes for example segfaults during live-migration with MQ enable, but in general virtually any request sent by qemu changing