From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Samuel Mendoza-Jonas <sam.mj@au1.ibm.com>
Cc: aik@ozlabs.ru, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V3] spapr: Fix stale HTAB during live migration
Date: Tue, 19 Aug 2014 09:23:27 +0100 [thread overview]
Message-ID: <20140819082326.GB2383@work-vm> (raw)
In-Reply-To: <1408429031-1716-1-git-send-email-sam.mj@au1.ibm.com>
* Samuel Mendoza-Jonas (sam.mj@au1.ibm.com) wrote:
> If a guest reboots during a running migration, changes to the
> hash page table are not necessarily updated on the destination.
> Opening a new file descriptor to the HTAB forces the migration
> handler to resend the entire table.
Yes I think that's safe.
> Signed-off-by: Samuel Mendoza-Jonas <sam.mj@au1.ibm.com>
> ---
> Changes in v3: Pointed out by David, htab_save_iterate could
> potentially try to read before htab_fd is open again.
> Leave opening the fd to the functions trying to read.
> Changes in v2: Forgot check on kvmppc_get_htab_fd return value
> hw/ppc/spapr.c | 25 +++++++++++++++++++++++++
> include/hw/ppc/spapr.h | 1 +
> 2 files changed, 26 insertions(+)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index 3a6d26d..5b41318 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -997,6 +997,10 @@ static void spapr_reset_htab(sPAPREnvironment *spapr)
> /* Kernel handles htab, we don't need to allocate one */
> spapr->htab_shift = shift;
> kvmppc_kern_htab = true;
> +
> + /* Check if we are overlapping a migration */
> + if (spapr->htab_fd > 0)
> + spapr->need_reset = true;
> } else {
> if (!spapr->htab) {
> /* Allocate an htab if we don't yet have one */
> @@ -1156,6 +1160,7 @@ static int htab_save_setup(QEMUFile *f, void *opaque)
> } else {
> assert(kvm_enabled());
>
> + spapr->need_reset = false;
> spapr->htab_fd = kvmppc_get_htab_fd(false);
> if (spapr->htab_fd < 0) {
> fprintf(stderr, "Unable to open fd for reading hash table from KVM: %s\n",
> @@ -1309,6 +1314,16 @@ static int htab_save_iterate(QEMUFile *f, void *opaque)
> if (!spapr->htab) {
> assert(kvm_enabled());
>
> + if (atomic_cmpxchg(&spapr->need_reset, true, false) == true) {
> + close(spapr->htab_fd);
> + spapr->htab_fd = kvmppc_get_htab_fd(false);
> + if (spapr->htab_fd < 0) {
> + fprintf(stderr, "Unable to open fd for reading hash table from KVM: %s\n",
> + strerror(errno));
Either perror or error_report() with the strerror would seem better.
> + return -1;
> + }
> + }
> +
Why not make a little function for this; it seems a bad idea to have two copies of
it.
Also, add a comment saying why you're reopening it.
Dave
> rc = kvmppc_save_htab(f, spapr->htab_fd,
> MAX_KVM_BUF_SIZE, MAX_ITERATION_NS);
> if (rc < 0) {
> @@ -1340,6 +1355,16 @@ static int htab_save_complete(QEMUFile *f, void *opaque)
>
> assert(kvm_enabled());
>
> + if (atomic_cmpxchg(&spapr->need_reset, true, false) == true) {
> + close(spapr->htab_fd);
> + spapr->htab_fd = kvmppc_get_htab_fd(false);
> + if (spapr->htab_fd < 0) {
> + fprintf(stderr, "Unable to open fd for reading hash table from KVM: %s\n",
> + strerror(errno));
> + return -1;
> + }
> + }
> +
> rc = kvmppc_save_htab(f, spapr->htab_fd, MAX_KVM_BUF_SIZE, -1);
> if (rc < 0) {
> return rc;
> diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
> index 0c2e3c5..9ab9827 100644
> --- a/include/hw/ppc/spapr.h
> +++ b/include/hw/ppc/spapr.h
> @@ -71,6 +71,7 @@ typedef struct sPAPREnvironment {
> int htab_save_index;
> bool htab_first_pass;
> int htab_fd;
> + bool need_reset;
>
> /* state for Dynamic Reconfiguration Connectors */
> sPAPRDrcEntry drc_table[SPAPR_DRC_TABLE_SIZE];
> --
> 1.9.3
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-08-19 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 6:17 [Qemu-devel] [PATCH V3] spapr: Fix stale HTAB during live migration Samuel Mendoza-Jonas
2014-08-19 8:23 ` Dr. David Alan Gilbert [this message]
2014-08-19 10:51 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
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=20140819082326.GB2383@work-vm \
--to=dgilbert@redhat.com \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sam.mj@au1.ibm.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 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.