From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, quintela@redhat.com
Cc: pbonzini@redhat.com, lvivier@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] migration/postcopy: Disable shared RAM
Date: Tue, 7 Mar 2017 18:36:35 +0000 [thread overview]
Message-ID: <20170307183637.21245-1-dgilbert@redhat.com> (raw)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Disable postcopy migration when there's shared RAM, we're
still figuring out the details. Without this patch
there's a chance it might appear to succeed in some
cases.
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Dr. David Alan Gilbert (2):
RAMBlocks: qemu_ram_is_shared
postcopy: Check for shared memory
exec.c | 5 +++++
include/exec/cpu-common.h | 1 +
migration/postcopy-ram.c | 18 ++++++++++++++++++
3 files changed, 24 insertions(+)
--
2.9.3
next reply other threads:[~2017-03-07 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 18:36 Dr. David Alan Gilbert (git) [this message]
2017-03-07 18:36 ` [Qemu-devel] [PATCH 1/2] RAMBlocks: qemu_ram_is_shared Dr. David Alan Gilbert (git)
2017-03-08 17:36 ` Halil Pasic
2017-03-08 17:38 ` Dr. David Alan Gilbert
2017-03-07 18:36 ` [Qemu-devel] [PATCH 2/2] postcopy: Check for shared memory Dr. David Alan Gilbert (git)
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=20170307183637.21245-1-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).