From: David Hildenbrand <david@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v3 08/13] migration/ram: Simplify host page handling in ram_load_postcopy()
Date: Fri, 6 Mar 2020 19:47:39 +0100 [thread overview]
Message-ID: <bfc208f7-bf3c-f7d0-33e0-b864163b61fd@redhat.com> (raw)
In-Reply-To: <29ffaf0b-55e6-53c4-2fd7-b3f0676c1412@redhat.com>
On 06.03.20 17:20, David Hildenbrand wrote:
> On 06.03.20 17:05, Dr. David Alan Gilbert wrote:
>> * David Hildenbrand (david@redhat.com) wrote:
>>> Add two new helper functions. This will in come handy once we want to
>>> handle ram block resizes while postcopy is active.
>>>
>>> Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>>> Cc: Juan Quintela <quintela@redhat.com>
>>> Cc: Peter Xu <peterx@redhat.com>
>>> Signed-off-by: David Hildenbrand <david@redhat.com>
>>> ---
>>> migration/ram.c | 54 ++++++++++++++++++++++++++++---------------------
>>> 1 file changed, 31 insertions(+), 23 deletions(-)
>>>
>>> diff --git a/migration/ram.c b/migration/ram.c
>>> index d5a4d69e1c..f815f4e532 100644
>>> --- a/migration/ram.c
>>> +++ b/migration/ram.c
>>> @@ -2734,6 +2734,20 @@ static inline void *host_from_ram_block_offset(RAMBlock *block,
>>> return block->host + offset;
>>> }
>>>
>>> +static void *host_page_from_ram_block_offset(RAMBlock *block,
>>> + ram_addr_t offset)
>>> +{
>>> + /* Note: Explicitly no check against offset_in_ramblock(). */
>>> + return (void *)QEMU_ALIGN_DOWN((uintptr_t)block->host + offset,
>>> + block->page_size);
>>> +}
>>> +
>>> +static ram_addr_t host_page_offset_from_ram_block_offset(RAMBlock *block,
>>> + ram_addr_t offset)
>>> +{
>>> + return ((uintptr_t)block->host + offset) & (block->page_size - 1);
>>> +}
>>> +
>>> static inline void *colo_cache_from_block_offset(RAMBlock *block,
>>> ram_addr_t offset)
>>> {
>>> @@ -3111,13 +3125,12 @@ static int ram_load_postcopy(QEMUFile *f)
>>> MigrationIncomingState *mis = migration_incoming_get_current();
>>> /* Temporary page that is later 'placed' */
>>> void *postcopy_host_page = mis->postcopy_tmp_page;
>>> - void *this_host = NULL;
>>> + void *host_page = NULL;
>>> bool all_zero = false;
>>> int target_pages = 0;
>>>
>>> while (!ret && !(flags & RAM_SAVE_FLAG_EOS)) {
>>> ram_addr_t addr;
>>> - void *host = NULL;
>>> void *page_buffer = NULL;
>>> void *place_source = NULL;
>>> RAMBlock *block = NULL;
>>> @@ -3143,9 +3156,12 @@ static int ram_load_postcopy(QEMUFile *f)
>>> if (flags & (RAM_SAVE_FLAG_ZERO | RAM_SAVE_FLAG_PAGE |
>>> RAM_SAVE_FLAG_COMPRESS_PAGE)) {
>>> block = ram_block_from_stream(f, flags);
>>> + if (!block) {
>>> + ret = -EINVAL;
>>
>> Could we have an error_report there, at the moment it would trigger
>> the one below.
>
> Makes sense, I'll add one!
My memory kicks in: This was dropped on purpose. ram_block_from_stream()
will print proper errors already.
Cheers!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-03-06 18:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 15:52 [PATCH v3 00/13] migrate/ram: Fix resizing RAM blocks while migrating David Hildenbrand
2020-02-26 15:52 ` [PATCH v3 01/13] util: vfio-helpers: Factor out and fix processing of existing ram blocks David Hildenbrand
2020-02-26 15:52 ` [PATCH v3 02/13] stubs/ram-block: Remove stubs that are no longer needed David Hildenbrand
2020-02-26 15:52 ` [PATCH v3 03/13] numa: Teach ram block notifiers about resizeable ram blocks David Hildenbrand
2020-02-26 15:52 ` [PATCH v3 04/13] numa: Make all callbacks of ram block notifiers optional David Hildenbrand
2020-02-26 15:52 ` [PATCH v3 05/13] migration/ram: Handle RAM block resizes during precopy David Hildenbrand
2020-02-26 15:52 ` [PATCH v3 06/13] exec: Relax range check in ram_block_discard_range() David Hildenbrand
2020-02-26 15:52 ` [PATCH v3 07/13] migration/ram: Discard RAM when growing RAM blocks after ram_postcopy_incoming_init() David Hildenbrand
2020-02-26 15:52 ` [PATCH v3 08/13] migration/ram: Simplify host page handling in ram_load_postcopy() David Hildenbrand
2020-03-06 16:05 ` Dr. David Alan Gilbert
2020-03-06 16:20 ` David Hildenbrand
2020-03-06 18:47 ` David Hildenbrand [this message]
2020-03-06 18:48 ` Dr. David Alan Gilbert
2020-02-26 15:53 ` [PATCH v3 09/13] migration/ram: Consolidate variable reset after placement " David Hildenbrand
2020-03-06 16:30 ` Dr. David Alan Gilbert
2020-03-06 19:09 ` David Hildenbrand
2020-03-06 19:11 ` Dr. David Alan Gilbert
2020-02-26 15:53 ` [PATCH v3 10/13] migration/ram: Handle RAM block resizes during postcopy David Hildenbrand
2020-03-06 16:56 ` Dr. David Alan Gilbert
2020-03-06 18:45 ` David Hildenbrand
2020-03-06 18:51 ` Dr. David Alan Gilbert
2020-02-26 15:53 ` [PATCH v3 11/13] migration/multifd: Print used_length of memory block David Hildenbrand
2020-03-06 16:57 ` Dr. David Alan Gilbert
2020-02-26 15:53 ` [PATCH v3 12/13] migration/ram: Use offset_in_ramblock() in range checks David Hildenbrand
2020-03-06 16:59 ` Dr. David Alan Gilbert
2020-02-26 15:53 ` [PATCH v3 13/13] migration/ram: Tolerate partially changed mappings in postcopy code David Hildenbrand
2020-02-26 16:06 ` Peter Xu
2020-02-26 16:08 ` David Hildenbrand
2020-02-26 16:26 ` Peter Xu
2020-02-26 16:34 ` David Hildenbrand
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=bfc208f7-bf3c-f7d0-33e0-b864163b61fd@redhat.com \
--to=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
/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).