Re: [PATCH v2 1/7] block-copy: streamline choice of copy_range vs. read/write

[Paolo Bonzini]

On 21/05/21 17:48, Vladimir Sementsov-Ogievskiy wrote:
> I keep it thinking about further moving qemu-img convert to block-copy. 
> But I don't even have a plan when to start this work. So, if we want to 
> do something around copy_range here to prepare for thread-safety, let's 
> just drop it for now as unused on top of "[PATCH v2 00/33] block: 
> publish backup-top filter" (you can take one patch that drop copy_range 
> support in backup to your series to not make a dependency). It's not 
> difficult to reimplement it later.

Then we'll have this same conversation later.  I would hope that this 
series goes in before yours.

Paolo