Extend the change_cb callback with a reason argument, and use it
to tell drivers about size changes.
Signed-off-by: Christoph Hellwig
Index: qemu/block.c
===
--- qemu.orig/block.c 2011-01-24 11:56:20.899004129 +0100
+++ qemu/block
Am 19.01.2011 18:02, schrieb Christoph Hellwig:
> Extend the change_cb callback with a reason argument, and use it
> to tell drivers about size changes.
>
> Signed-off-by: Christoph Hellwig
>
> Index: qemu/block.c
> ===
> --- qemu.o
On Thu, Jan 20, 2011 at 09:14:17AM +, Stefan Hajnoczi wrote:
> Cool, this is much nicer than stashing away state like
> bs->media_changed = 1. I just took a peek to see if we can remove
> that field completely but IDE seems to use it internally.
I think we could get rid of it in generic code,
On Wed, Jan 19, 2011 at 5:02 PM, Christoph Hellwig wrote:
> Extend the change_cb callback with a reason argument, and use it
> to tell drivers about size changes.
>
> Signed-off-by: Christoph Hellwig
>
> Index: qemu/block.c
> ===
> -
Extend the change_cb callback with a reason argument, and use it
to tell drivers about size changes.
Signed-off-by: Christoph Hellwig
Index: qemu/block.c
===
--- qemu.orig/block.c 2011-01-18 20:54:45.246021572 +0100
+++ qemu/block
> Do we want to check to ensure the size_changed flag isn't set before
> doing a second resize event? I'm wondering if the truncate takes
> $longtime and user gets impatient and issues a second resize command.
> How should we respond? Ignore it? queue it up?
The truncate is synchronous and the
* Christoph Hellwig [2011-01-14 10:27]:
> Add a new size_changed flag in the BlockDriverState and call the
> change_cb callback to notify drivers about a size change.
>
> Signed-off-by: Christoph Hellwig
>
> Index: qemu/block.c
> =
Add a new size_changed flag in the BlockDriverState and call the
change_cb callback to notify drivers about a size change.
Signed-off-by: Christoph Hellwig
Index: qemu/block.c
===
--- qemu.orig/block.c 2011-01-14 17:05:49.52700336
