[Qemu-devel] [PATCH v3 4/9] block: Introduce bdrv_dirty_bitmap_granularity()

2014-03-17 Thread Fam Zheng
This returns the granularity (in sectors) of dirty bitmap. Signed-off-by: Fam Zheng Reviewed-by: Benoit Canet --- block.c | 6 ++ include/block/block.h | 2 ++ 2 files changed, 8 insertions(+) diff --git a/block.c b/block.c index e32da75..ecc0dad 100644 --- a/block.c +++ b/bl

[Qemu-devel] [PATCH v3 9/9] qapi: Add transaction support to dirty-bitmap-{add, disable}

2014-03-17 Thread Fam Zheng
This adds dirty-bitmap-add and dirty-bitmap-disable to transactions. With this, user can stop a dirty bitmap, start backup of it, and start another dirty bitmap atomically, so that the dirty bitmap is tracked incrementally and we don't miss any write. Signed-off-by: Fam Zheng --- blockdev.c

[Qemu-devel] [PATCH v3 7/9] qmp: Add dirty-bitmap-enable and dirty-bitmap-disable

2014-03-17 Thread Fam Zheng
This allows to put the dirty bitmap into a disabled state where no more writes will be tracked. It will be used before backup or writing to persistent file. Signed-off-by: Fam Zheng --- block.c | 15 +++ blockdev.c| 44 ++

[Qemu-devel] [PATCH v3 5/9] hbitmap: Add hbitmap_copy

2014-03-17 Thread Fam Zheng
This makes a deep copy of an HBitmap. Signed-off-by: Fam Zheng --- include/qemu/hbitmap.h | 8 util/hbitmap.c | 16 2 files changed, 24 insertions(+) diff --git a/include/qemu/hbitmap.h b/include/qemu/hbitmap.h index 550d7ce..b645cfc 100644 --- a/include/qemu/

[Qemu-devel] [PATCH v3 1/9] qapi: Add optional field "name" to block dirty bitmap

2014-03-17 Thread Fam Zheng
This field will be set for user created dirty bitmap. Also pass in an error pointer to bdrv_create_dirty_bitmap, so when a name is already taken on this BDS, it can report an error message. This is not global check, two BDSes can have dirty bitmap with a common name. Implemented bdrv_find_dirty_bi

[Qemu-devel] [PATCH v3 0/9] QMP: Introduce incremental drive-backup with in-memory dirty bitmap

2014-03-17 Thread Fam Zheng
Introduction This implements incremental backup. A convenient option "bitmap-use-mode" for drive-backup is introduced since v1. Commands A new sync mode for drive-backup is introduced: drive-backup device=.. mode=.. sync=dirty-bitmap bitmap=bitmap0 bitmap-use-mode=re

Re: [Qemu-devel] [PATCH v4 16/21] target-arm: Implement SP_EL0, SP_EL1

2014-03-17 Thread Peter Crosthwaite
On Mon, Mar 17, 2014 at 5:02 PM, Peter Crosthwaite wrote: > On Fri, Mar 7, 2014 at 5:33 AM, Peter Maydell > wrote: >> Implement handling for the AArch64 SP_EL0 system register. >> This holds the EL0 stack pointer, and is only accessible when >> it's not being used as the stack pointer, ie when w

Re: [Qemu-devel] [PATCH v4 01/21] target-arm: Split out private-to-target functions into internals.h

2014-03-17 Thread Peter Crosthwaite
On Fri, Mar 7, 2014 at 5:32 AM, Peter Maydell wrote: > Currently cpu.h defines a mixture of functions and types needed by > the rest of QEMU and those needed only by files within target-arm/. > Split the latter out into a new header so they aren't needlessly > exposed further than required. > > Si

Re: [Qemu-devel] [PATCH v4 21/21] hw/arm/virt: Add support for Cortex-A57

2014-03-17 Thread Peter Crosthwaite
On Fri, Mar 7, 2014 at 5:33 AM, Peter Maydell wrote: > Support the Cortex-A57 in the virt machine model. > > Signed-off-by: Peter Maydell > --- > This should perhaps not be just stealing the a15mpcore_priv > on the basis that it's a GICv2... Wont this mean you gets lots of extraneous hardware? A

Re: [Qemu-devel] [PATCH v4 18/21] target-arm: Move arm_log_exception() into internals.h

2014-03-17 Thread Peter Crosthwaite
On Fri, Mar 7, 2014 at 5:33 AM, Peter Maydell wrote: > Move arm_log_exception() into internals.h so we can use it from > helper-a64.c for the AArch64 exception entry code. > > Signed-off-by: Peter Maydell Reviewed-by: Peter Crosthwaite > --- > target-arm/helper.c| 31 -

Re: [Qemu-devel] [PATCH v4 16/21] target-arm: Implement SP_EL0, SP_EL1

2014-03-17 Thread Peter Crosthwaite
On Fri, Mar 7, 2014 at 5:33 AM, Peter Maydell wrote: > Implement handling for the AArch64 SP_EL0 system register. > This holds the EL0 stack pointer, and is only accessible when > it's not being used as the stack pointer, ie when we're in EL1 > and EL1 is using its own stack pointer. We also provi

<    1   2   3   4