From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
jan.kiszka@siemens.com, xen-devel@lists.xensource.com,
avi@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/6] vl.c: do not save the RAM state when Xen is enabled
Date: Mon, 23 Jan 2012 09:58:51 -0600 [thread overview]
Message-ID: <4F1D83BB.8070209@codemonkey.ws> (raw)
In-Reply-To: <1327080085-8673-1-git-send-email-stefano.stabellini@eu.citrix.com>
On 01/20/2012 11:21 AM, Stefano Stabellini wrote:
> From: Anthony PERARD<anthony.perard@citrix.com>
>
> In the Xen case, the guest RAM is not handle by QEMU, and it is saved by
> Xen tools.
> So, we just avoid to register the RAM save state handler.
>
> Signed-off-by: Anthony PERARD<anthony.perard@citrix.com>
> Signed-off-by: Stefano Stabellini<stefano.stabellini@eu.citrix.com>
> ---
> vl.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/vl.c b/vl.c
> index ba55b35..6f0435b 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -3270,8 +3270,10 @@ int main(int argc, char **argv, char **envp)
> default_drive(default_sdcard, snapshot, machine->use_scsi,
> IF_SD, 0, SD_OPTS);
>
> - register_savevm_live(NULL, "ram", 0, 4, NULL, ram_save_live, NULL,
> - ram_load, NULL);
> + if (!xen_enabled()) {
> + register_savevm_live(NULL, "ram", 0, 4, NULL, ram_save_live, NULL,
> + ram_load, NULL);
> + }
Why not introduce new Xen specific commands like I suggested on IRC?
This sort of change is extremely non-intuitive. We should do as much as we can
to avoid magic #ifdefs like this.
Regards,
Anthony Liguori
>
> if (nb_numa_nodes> 0) {
> int i;
next prev parent reply other threads:[~2012-01-23 15:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 17:20 [Qemu-devel] [PATCH v4 0/6] save/restore on Xen Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 1/6] vl.c: do not save the RAM state when Xen is enabled Stefano Stabellini
2012-01-23 15:58 ` Anthony Liguori [this message]
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 2/6] xen mapcache: check if memory region has moved Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 3/6] Set runstate to INMIGRATE earlier Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 4/6] cirrus_vga: do not reset videoram on resume Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 5/6] xen: record physmap changes to xenstore Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 6/6] xen: change memory access behavior during migration Stefano Stabellini
2012-01-20 17:59 ` [Qemu-devel] [PATCH v4 0/6] save/restore on Xen Jan Kiszka
2012-01-23 10:47 ` Stefano Stabellini
2012-01-23 11:50 ` Jan Kiszka
2012-01-23 11:59 ` Stefano Stabellini
2012-01-23 12:10 ` Jan Kiszka
2012-01-23 14:46 ` Stefano Stabellini
2012-01-23 15:46 ` Jan Kiszka
2012-01-23 16:16 ` Stefano Stabellini
2012-01-23 16:22 ` Anthony Liguori
2012-01-23 17:13 ` Jan Kiszka
2012-01-23 17:18 ` Anthony Liguori
2012-01-23 17:31 ` Jan Kiszka
2012-01-23 17:36 ` Anthony Liguori
2012-01-24 10:21 ` Gerd Hoffmann
2012-01-24 11:13 ` Avi Kivity
2012-01-24 12:00 ` Stefano Stabellini
2012-01-24 15:39 ` Avi Kivity
2012-01-24 13:18 ` Anthony Liguori
2012-01-24 15:43 ` Avi Kivity
2012-01-24 13:25 ` Anthony Liguori
2012-01-24 15:47 ` Avi Kivity
2012-01-24 11:10 ` Avi Kivity
2012-01-24 11:27 ` Paolo Bonzini
2012-01-24 11:32 ` Avi Kivity
2012-01-24 11:44 ` Paolo Bonzini
2012-01-24 15:48 ` Avi Kivity
2012-01-24 11:52 ` Stefano Stabellini
2012-01-24 13:15 ` Anthony Liguori
2012-01-24 13:14 ` Anthony Liguori
2012-01-24 15:56 ` Avi Kivity
2012-01-24 17:51 ` Anthony Liguori
2012-01-23 16:00 ` Anthony Liguori
2012-01-23 16:46 ` Stefano Stabellini
2012-01-23 16:54 ` Anthony Liguori
2012-01-23 17:05 ` Stefano Stabellini
2012-01-23 17:07 ` Anthony Liguori
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=4F1D83BB.8070209@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=anthony.perard@citrix.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).