From: lirans@il.ibm.com
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 1/3] Expose a mechanisem to trace block writes
Date: Mon, 7 Sep 2009 12:23:09 +0300 [thread overview]
Message-ID: <12523153891813-git-send-email-lirans@il.ibm.com> (raw)
To support live migration without shared storage we need to be able to trace
writes to disk while migrating. This Patch expose handler registration for
above components to be notified about block writes.
diff --git a/block.c b/block.c
index cefbe77..b13da08 100644
--- a/block.c
+++ b/block.c
@@ -63,6 +63,8 @@ BlockDriverState *bdrv_first;
static BlockDriver *first_drv;
+static BlockDriverDirtyHandler *bdrv_dirty_handler = NULL;
+
int path_is_absolute(const char *path)
{
const char *p;
@@ -613,6 +615,10 @@ int bdrv_write(BlockDriverState *bs, int64_t sector_num,
if (bdrv_check_request(bs, sector_num, nb_sectors))
return -EIO;
+ if(bdrv_dirty_handler != NULL) {
+ bdrv_dirty_handler(bs, sector_num, nb_sectors);
+ }
+
return drv->bdrv_write(bs, sector_num, buf, nb_sectors);
}
@@ -1144,6 +1150,11 @@ int bdrv_write_compressed(BlockDriverState *bs, int64_t sector_num,
return -ENOTSUP;
if (bdrv_check_request(bs, sector_num, nb_sectors))
return -EIO;
+
+ if(bdrv_dirty_handler != NULL) {
+ bdrv_dirty_handler(bs, sector_num, nb_sectors);
+ }
+
return drv->bdrv_write_compressed(bs, sector_num, buf, nb_sectors);
}
@@ -1338,7 +1349,11 @@ BlockDriverAIOCB *bdrv_aio_writev(BlockDriverState *bs, int64_t sector_num,
return NULL;
if (bdrv_check_request(bs, sector_num, nb_sectors))
return NULL;
-
+
+ if(bdrv_dirty_handler != NULL) {
+ bdrv_dirty_handler(bs, sector_num, nb_sectors);
+ }
+
ret = drv->bdrv_aio_writev(bs, sector_num, qiov, nb_sectors,
cb, opaque);
@@ -1632,6 +1647,17 @@ BlockDriverAIOCB *bdrv_aio_ioctl(BlockDriverState *bs,
return NULL;
}
+void register_bdrv_dirty_tracking(BlockDriverDirtyHandler *dirty_handler)
+{
+ bdrv_dirty_handler = dirty_handler;
+}
+
+void unregister_bdrv_dirty_tracking(void)
+{
+ bdrv_dirty_handler = NULL;
+}
+
+
void *qemu_blockalign(BlockDriverState *bs, size_t size)
{
return qemu_memalign((bs && bs->buffer_alignment) ? bs->buffer_alignment : 512, size);
diff --git a/block.h b/block.h
index 71e87fc..7f7db12 100644
--- a/block.h
+++ b/block.h
@@ -79,6 +79,8 @@ void bdrv_register(BlockDriver *bdrv);
typedef struct BlockDriverAIOCB BlockDriverAIOCB;
typedef void BlockDriverCompletionFunc(void *opaque, int ret);
+typedef void BlockDriverDirtyHandler(BlockDriverState *bs, int64_t sector,
+ int sector_num);
BlockDriverAIOCB *bdrv_aio_readv(BlockDriverState *bs, int64_t sector_num,
QEMUIOVector *iov, int nb_sectors,
BlockDriverCompletionFunc *cb, void *opaque);
@@ -165,4 +167,7 @@ int bdrv_put_buffer(BlockDriverState *bs, const uint8_t *buf,
int bdrv_get_buffer(BlockDriverState *bs, uint8_t *buf, int64_t pos, int size);
+void register_bdrv_dirty_tracking(BlockDriverDirtyHandler *dirty_handler);
+void unregister_bdrv_dirty_tracking(void);
+
#endif
diff --git a/block_int.h b/block_int.h
index 830b7e9..c066485 100644
--- a/block_int.h
+++ b/block_int.h
@@ -156,6 +156,7 @@ struct BlockDriverState {
int cyls, heads, secs, translation;
int type;
char device_name[32];
+ void *dirty_control;
BlockDriverState *next;
void *private;
};
next reply other threads:[~2009-09-07 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 9:23 lirans [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-10 10:24 [Qemu-devel] [PATCH 1/3] Expose a mechanisem to trace block writes lirans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12523153891813-git-send-email-lirans@il.ibm.com \
--to=lirans@il.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).