From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: miguel.filho@gmail.com
Subject: [Qemu-devel] Re: [PATCH] savevm: Reset last block info at beginning of each save
Date: Thu, 05 Aug 2010 13:13:34 -0600 [thread overview]
Message-ID: <1281035614.6598.312.camel@x201> (raw)
In-Reply-To: <20100720141808.9372.30011.stgit@localhost6.localdomain6>
Bump, this really should make 0.13. Thanks,
Alex
On Tue, 2010-07-20 at 08:19 -0600, Alex Williamson wrote:
> 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>
> ---
>
> Anthony, this fixes a regression caused by the new migration code and
> should be queued for 0.13. Thanks,
>
> Alex
>
> 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) {
>
prev parent reply other threads:[~2010-08-05 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 14:19 [Qemu-devel] [PATCH] savevm: Reset last block info at beginning of each save Alex Williamson
2010-08-05 19:13 ` Alex Williamson [this message]
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=1281035614.6598.312.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=miguel.filho@gmail.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 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).