From: Paolo Bonzini <pbonzini@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, thuth@redhat.com,
dgibson@redhat.com
Subject: Re: [Qemu-devel] [PATCH] spapr: fix spapr-nvram migration
Date: Thu, 21 Jul 2016 08:12:43 -0400 (EDT) [thread overview]
Message-ID: <559834123.9435733.1469103163593.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1469102746-20588-1-git-send-email-lvivier@redhat.com>
> When spapr-nvram is backed by a file using pflash interface,
> migration fails on the destination guest with assert:
>
> bdrv_co_pwritev: Assertion `!(bs->open_flags & 0x0800)' failed.
>
> This avoids the problem by delaying the pflash update until after
> the device loads complete.
>
> This fix is similar to the one for the pflash_cfi01 migration:
>
> 90c647d Fix pflash migration
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> hw/nvram/spapr_nvram.c | 23 +++++++++++++++--------
> 1 file changed, 15 insertions(+), 8 deletions(-)
>
> diff --git a/hw/nvram/spapr_nvram.c b/hw/nvram/spapr_nvram.c
> index 019f25d..4de5f70 100644
> --- a/hw/nvram/spapr_nvram.c
> +++ b/hw/nvram/spapr_nvram.c
> @@ -39,6 +39,7 @@ typedef struct sPAPRNVRAM {
> uint32_t size;
> uint8_t *buf;
> BlockBackend *blk;
> + VMChangeStateEntry *vmstate;
> } sPAPRNVRAM;
>
> #define TYPE_VIO_SPAPR_NVRAM "spapr-nvram"
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Perhaps spapr_nvram.c should have been in hw/block, or pflash should be
moved to hw/nvram.
Paolo
> @@ -185,19 +186,25 @@ static int spapr_nvram_pre_load(void *opaque)
> return 0;
> }
>
> +static void postload_update_cb(void *opaque, int running, RunState state)
> +{
> + sPAPRNVRAM *nvram = opaque;
> +
> + /* This is called after bdrv_invalidate_cache_all. */
> +
> + qemu_del_vm_change_state_handler(nvram->vmstate);
> + nvram->vmstate = NULL;
> +
> + blk_pwrite(nvram->blk, 0, nvram->buf, nvram->size, 0);
> +}
> +
> static int spapr_nvram_post_load(void *opaque, int version_id)
> {
> sPAPRNVRAM *nvram = VIO_SPAPR_NVRAM(opaque);
>
> if (nvram->blk) {
> - int alen = blk_pwrite(nvram->blk, 0, nvram->buf, nvram->size, 0);
> -
> - if (alen < 0) {
> - return alen;
> - }
> - if (alen != nvram->size) {
> - return -1;
> - }
> + nvram->vmstate =
> qemu_add_vm_change_state_handler(postload_update_cb,
> + nvram);
> }
>
> return 0;
> --
> 2.5.5
>
>
next prev parent reply other threads:[~2016-07-21 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 12:05 [Qemu-devel] [PATCH] spapr: fix spapr-nvram migration Laurent Vivier
2016-07-21 12:12 ` Paolo Bonzini [this message]
2016-07-22 6:47 ` David Gibson
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=559834123.9435733.1469103163593.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgibson@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).