From: David Hildenbrand <david@redhat.com>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] migration: Calculate ram size once
Date: Wed, 11 May 2022 11:22:30 +0200 [thread overview]
Message-ID: <94da21f4-60df-9cf9-3317-b762760ecf80@redhat.com> (raw)
In-Reply-To: <20220510231708.7197-3-quintela@redhat.com>
On 11.05.22 01:17, Juan Quintela wrote:
> We are recalculating ram size continously, when we know that it don't
> change during migration. Create a field in RAMState to track it.
We do have resizable RAM, which triggers ram_mig_ram_block_resized() on
resizes when changing block->used_length.
ram_mig_ram_block_resized() aborts migration when we detect a resize on
the source. I assume that is what you care about here, right?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-05-11 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 23:17 [PATCH 0/2] migration: Store ram size value Juan Quintela
2022-05-10 23:17 ` [PATCH 1/2] migration: Split ram_bytes_total_common() in two functions Juan Quintela
2022-05-10 23:17 ` [PATCH 2/2] migration: Calculate ram size once Juan Quintela
2022-05-11 9:22 ` David Hildenbrand [this message]
2022-05-16 10:04 ` Juan Quintela
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=94da21f4-60df-9cf9-3317-b762760ecf80@redhat.com \
--to=david@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).