On Fri, 01/22 15:05, Vladimir Sementsov-Ogievskiy wrote: > >In my migration series I need iterators, get granularity, and > >something like hbitmap_count for meta bitmaps. You can add them > >here if you want, or I can add them in my series.
Okay, I can add that. I have one more question on the interface: what dirty bitmaps are going to be migrated? At this moment there are dirty bitmaps created by block jobs (drive-mirror), and in-memory dirty bitmaps created for incremental backup; later there will be persistent dirty bitmaps owned by block drivers (extended version of qcow2, and in QBM driver I'm working on). Which of them are subject of migration in your series? I'm asking because I want to know whether we need to implement multiple meta bitmaps on one block dirty bitmap. Fam
