[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 1/4] QMP, Introduce set-global-dirty-log command.

To: Anthony PERARD <anthony.perard@xxxxxxxxxx>
From: Avi Kivity <avi@xxxxxxxxxx>
Date: Tue, 17 Jul 2012 16:58:49 +0300
Cc: Anthony Liguori <aliguori@xxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>, QEMU-devel <qemu-devel@xxxxxxxxxx>, Luiz Capitulino <lcapitulino@xxxxxxxxxx>
Delivery-date: Tue, 17 Jul 2012 13:59:17 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 07/17/2012 04:30 PM, Anthony PERARD wrote:
> This command is used during a migration of a guest under Xen. It calls
> memory_global_dirty_log_start or memory_global_dirty_log_stop according to the
> argument pass to the command.

Is the command truly needed?  Can't it come from the xen library you
link to?


-- 
error compiling committee.c: too many arguments to function



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH 1/4] QMP, Introduce set-global-dirty-log command.
  - From: Stefano Stabellini

References:
- [Xen-devel] [PATCH 0/4] Xen, introducing dirty log for migration.
  - From: Anthony PERARD
- [Xen-devel] [PATCH 1/4] QMP, Introduce set-global-dirty-log command.
  - From: Anthony PERARD

Prev by Date: Re: [Xen-devel] [Qemu-devel] [PATCH 1/4] QMP, Introduce set-global-dirty-log command.
Next by Date: Re: [Xen-devel] [Qemu-devel] [PATCH 3/4] exec, memory: Call to xen_modified_memory.
Previous by thread: Re: [Xen-devel] [Qemu-devel] [PATCH 1/4] QMP, Introduce set-global-dirty-log command.
Next by thread: Re: [Xen-devel] [PATCH 1/4] QMP, Introduce set-global-dirty-log command.
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.