All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Xen Devel <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	QEMU-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V5 1/5] QMP, Introduce xen-set-global-dirty-log command.
Date: Tue, 02 Oct 2012 10:56:30 -0600	[thread overview]
Message-ID: <506B1CBE.6050408@redhat.com> (raw)
In-Reply-To: <1349196747-30410-2-git-send-email-anthony.perard@citrix.com>

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

On 10/02/2012 10:52 AM, 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.
> 
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> Reviewed-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
>  qapi-schema.json | 13 +++++++++++++
>  qmp-commands.hx  | 24 ++++++++++++++++++++++++
>  xen-all.c        | 15 +++++++++++++++
>  xen-stub.c       |  5 +++++
>  4 files changed, 57 insertions(+)
> 
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 14e4419..696f45a 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -1956,6 +1956,19 @@
>  { 'command': 'xen-save-devices-state', 'data': {'filename': 'str'} }
>  
>  ##
> +# @xen-set-global-dirty-log
> +#
> +# Enable or disable the global dirty log mode.
> +#
> +# @enable: true to enable, false to disable.
> +#
> +# Returns: nothing
> +#
> +# Since: 1.2

1.3

-- 
Eric Blake   eblake@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 617 bytes --]

  reply	other threads:[~2012-10-02 16:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 16:52 [Qemu-devel] [PATCH V5 0/5] Xen, introducing dirty log for migration Anthony PERARD
2012-10-02 16:52 ` [Qemu-devel] [PATCH V5 1/5] QMP, Introduce xen-set-global-dirty-log command Anthony PERARD
2012-10-02 16:56   ` Eric Blake [this message]
2012-10-02 18:09     ` Anthony PERARD
2012-10-02 16:56   ` Eric Blake
2012-10-02 16:52 ` Anthony PERARD
2012-10-02 16:52 ` [Qemu-devel] [PATCH V5 2/5] xen: Introduce xen_modified_memory Anthony PERARD
2012-10-02 16:52   ` Anthony PERARD
2012-10-02 16:52 ` [PATCH V5 3/5] exec: Introduce helper to set dirty flags Anthony PERARD
2012-10-02 16:52 ` [Qemu-devel] " Anthony PERARD
2012-10-02 16:52 ` [PATCH V5 4/5] exec, memory: Call to xen_modified_memory Anthony PERARD
2012-10-02 16:52 ` [Qemu-devel] " Anthony PERARD
2012-10-02 16:53   ` Avi Kivity
2012-10-02 16:53   ` [Qemu-devel] " Avi Kivity
2012-10-02 16:52 ` [PATCH V5 5/5] xen: Set the vram dirty when an error occur Anthony PERARD
2012-10-02 16:52 ` [Qemu-devel] " Anthony PERARD
  -- strict thread matches above, loose matches on Subject: below --
2012-10-02 18:21 [Qemu-devel] [PATCH V5 0/5] Xen, introducing dirty log for migration Anthony PERARD
2012-10-02 18:21 ` [Qemu-devel] [PATCH V5 1/5] QMP, Introduce xen-set-global-dirty-log command Anthony PERARD

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=506B1CBE.6050408@redhat.com \
    --to=eblake@redhat.com \
    --cc=anthony.perard@citrix.com \
    --cc=avi@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.