Expose a mechanism to trace block writes
authorlirans@il.ibm.com <lirans@il.ibm.com>
Mon, 2 Nov 2009 13:40:41 +0000 (15:40 +0200)
committerAnthony Liguori <aliguori@us.ibm.com>
Tue, 17 Nov 2009 14:03:31 +0000 (08:03 -0600)
commit3592036c9a3e681b62ef3dafb9307167798be251
tree3b2c8712ea67b77d1a7a4b86a532744f9daa2aac
parent9f312659f4d3a958774706b6f69eb5b6c08f617a
Expose a mechanism to trace block writes

To support live migration without shared storage we need to be able to trace
writes to disk while migrating. This Patch expose dirty block tracking per
device to be polled from upper layer.

Changes from v4:
- Register dirty tracking for each block device.
- Minor coding style issues.
- Block.c will now manage a dirty bitmap per device once
  bdrv_set_dirty_tracking() is called. Bitmap is polled by the upper
  layer (block-migration.c).

Signed-off-by: Liran Schour <lirans@il.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
block.c
block.h
block_int.h