From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: aliguori@us.ibm.com, Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4] savevm: Reset last block info at beginning of each save
Date: Thu, 19 Aug 2010 10:20:09 -0500 [thread overview]
Message-ID: <4C6D4BA9.6080801@codemonkey.ws> (raw)
In-Reply-To: <1282223922-5971-5-git-send-email-lcapitulino@redhat.com>
On 08/19/2010 08:18 AM, Luiz Capitulino wrote:
> From: Alex Williamson<alex.williamson@redhat.com>
>
> If we save more than once we need to reset the last block info or else
> only the first save has the actual block info and each subsequent save
> will only use continue flags, making them unloadable independently.
>
> Found-by: Miguel Di Ciurcio Filho<miguel.filho@gmail.com>
> Signed-off-by: Alex Williamson<alex.williamson@redhat.com>
> Acked-by: Glauber Costa<glommer@redhat.com>
> Signed-off-by: Luiz Capitulino<lcapitulino@redhat.com>
>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
> arch_init.c | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/arch_init.c b/arch_init.c
> index 47bb4b2..e0bd18c 100644
> --- a/arch_init.c
> +++ b/arch_init.c
> @@ -104,10 +104,11 @@ static int is_dup_page(uint8_t *page, uint8_t ch)
> return 1;
> }
>
> +static RAMBlock *last_block;
> +static ram_addr_t last_offset;
> +
> static int ram_save_block(QEMUFile *f)
> {
> - static RAMBlock *last_block = NULL;
> - static ram_addr_t last_offset = 0;
> RAMBlock *block = last_block;
> ram_addr_t offset = last_offset;
> ram_addr_t current_addr;
> @@ -231,6 +232,8 @@ int ram_save_live(Monitor *mon, QEMUFile *f, int stage, void *opaque)
> if (stage == 1) {
> RAMBlock *block;
> bytes_transferred = 0;
> + last_block = NULL;
> + last_offset = 0;
>
> /* Make sure all dirty bits are set */
> QLIST_FOREACH(block,&ram_list.blocks, next) {
>
next prev parent reply other threads:[~2010-08-19 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 13:18 [Qemu-devel] [STABLE 0.13 0/4][PULL]: Migration fixes Luiz Capitulino
2010-08-19 13:18 ` [Qemu-devel] [PATCH 1/4] set proper migration status on ->write error (v5) Luiz Capitulino
2010-08-19 15:19 ` Anthony Liguori
2010-08-19 13:18 ` [Qemu-devel] [PATCH 2/4] QEMUFileBuffered: indicate that we're ready when the underlying file is ready Luiz Capitulino
2010-08-19 13:18 ` [Qemu-devel] [PATCH 3/4] migration: Accept 'cont' only after successful incoming migration Luiz Capitulino
2010-08-19 13:18 ` [Qemu-devel] [PATCH 4/4] savevm: Reset last block info at beginning of each save Luiz Capitulino
2010-08-19 15:20 ` Anthony Liguori [this message]
2010-08-19 13:44 ` [Qemu-devel] Re: [STABLE 0.13 0/4][PULL]: Migration fixes Anthony Liguori
2010-08-19 13:51 ` Luiz Capitulino
2010-08-19 14:01 ` 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=4C6D4BA9.6080801@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alex.williamson@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.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 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.