From: Avi Kivity <avi@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Xen Devel <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
QEMU-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/4] QMP, Introduce set-global-dirty-log command.
Date: Tue, 17 Jul 2012 16:58:49 +0300 [thread overview]
Message-ID: <50056F99.6090603@redhat.com> (raw)
In-Reply-To: <1342531805-29894-2-git-send-email-anthony.perard@citrix.com>
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
next prev parent reply other threads:[~2012-07-17 13:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 13:30 [Qemu-devel] [PATCH 0/4] Xen, introducing dirty log for migration Anthony PERARD
2012-07-17 13:30 ` [Qemu-devel] [PATCH 1/4] QMP, Introduce set-global-dirty-log command Anthony PERARD
2012-07-17 13:57 ` Eric Blake
2012-07-17 13:58 ` Avi Kivity [this message]
2012-07-17 17:58 ` Stefano Stabellini
2012-07-18 8:30 ` Avi Kivity
2012-07-17 13:30 ` [Qemu-devel] [PATCH 2/4] xen: Introduce xen_modified_memory Anthony PERARD
2012-07-17 13:30 ` [Qemu-devel] [PATCH 3/4] exec, memory: Call to xen_modified_memory Anthony PERARD
2012-07-17 13:37 ` Avi Kivity
2012-07-17 13:59 ` Anthony PERARD
2012-07-17 14:44 ` Avi Kivity
2012-07-17 18:36 ` Stefano Stabellini
2012-07-18 8:32 ` Avi Kivity
2012-07-19 11:41 ` Anthony PERARD
2012-07-19 11:50 ` Avi Kivity
2012-07-19 14:27 ` Anthony PERARD
2012-07-17 18:06 ` Stefano Stabellini
2012-07-19 12:34 ` Paolo Bonzini
2012-07-19 15:37 ` Stefano Stabellini
2012-07-19 15:41 ` Anthony PERARD
2012-07-17 13:30 ` [Qemu-devel] [PATCH 4/4] xen: Always set the vram dirty during migration Anthony PERARD
2012-07-17 18:25 ` Stefano Stabellini
2012-07-17 18:30 ` Stefano Stabellini
2012-07-20 14:11 ` Anthony PERARD
2012-07-20 15:47 ` Stefano Stabellini
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=50056F99.6090603@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=anthony.perard@citrix.com \
--cc=lcapitulino@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 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).