Re: [PATCH v2 5/5] libvhost-user: handle removal of identical regions

2022-01-10 Thread Raphael Norwitz
On Mon, Jan 10, 2022 at 09:58:01AM +0100, David Hildenbrand wrote: > On 06.01.22 07:47, Raphael Norwitz wrote: > > Today if QEMU (or any other VMM) has sent multiple copies of the same > > region to a libvhost-user based backend and then attempts to remove the > > region, only one instance of the r

Re: [PATCH v2 5/5] libvhost-user: handle removal of identical regions

2022-01-10 Thread Stefan Hajnoczi
On Thu, Jan 06, 2022 at 06:47:36AM +, Raphael Norwitz wrote: > Today if QEMU (or any other VMM) has sent multiple copies of the same > region to a libvhost-user based backend and then attempts to remove the > region, only one instance of the region will be removed, leaving stale > copies of the

Re: [PATCH v2 5/5] libvhost-user: handle removal of identical regions

2022-01-10 Thread David Hildenbrand
On 06.01.22 07:47, Raphael Norwitz wrote: > Today if QEMU (or any other VMM) has sent multiple copies of the same > region to a libvhost-user based backend and then attempts to remove the > region, only one instance of the region will be removed, leaving stale > copies of the region in dev->regions

[PATCH v2 5/5] libvhost-user: handle removal of identical regions

2022-01-05 Thread Raphael Norwitz
Today if QEMU (or any other VMM) has sent multiple copies of the same region to a libvhost-user based backend and then attempts to remove the region, only one instance of the region will be removed, leaving stale copies of the region in dev->regions[]. This change resolves this by having vu_rem_me