qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Steven Sistare <steven.sistare@oracle.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Fabiano Rosas <farosas@suse.de>,
	Philippe Mathieu-Daude <philmd@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH V2] migration: ram block cpr blockers
Date: Fri, 14 Feb 2025 16:44:40 -0500	[thread overview]
Message-ID: <49c83982-46bf-4ab3-a683-776d4c342b27@oracle.com> (raw)
In-Reply-To: <7e781592-ea91-4a3a-9855-8e5479e0b61e@redhat.com>

On 2/14/2025 4:21 PM, David Hildenbrand wrote:
> On 14.02.25 21:12, Steve Sistare wrote:
>> Unlike cpr-reboot mode, cpr-transfer mode cannot save volatile ram blocks
>> in the migration stream file and recreate them later, because the physical
>> memory for the blocks is pinned and registered for vfio.  Add a blocker
>> for volatile ram blocks.
>>
>> Also add a blocker for RAM_GUEST_MEMFD.  Preserving guest_memfd may be
>> sufficient for CPR, but it has not been tested yet.
>>
>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
>> Reviewed-by: Fabiano Rosas <farosas@suse.de>
>> ---
>>   include/exec/memory.h   |  3 +++
>>   include/exec/ramblock.h |  1 +
>>   migration/savevm.c      |  2 ++
>>   system/physmem.c        | 68 +++++++++++++++++++++++++++++++++++++++++++++++++
>>   4 files changed, 74 insertions(+)
>>
>> diff --git a/include/exec/memory.h b/include/exec/memory.h
>> index 9f73b59..ea5d33a 100644
>> --- a/include/exec/memory.h
>> +++ b/include/exec/memory.h
>> @@ -3184,6 +3184,9 @@ bool ram_block_discard_is_disabled(void);
>>    */
>>   bool ram_block_discard_is_required(void);
>> +void ram_block_add_cpr_blocker(RAMBlock *rb, Error **errp);
>> +void ram_block_del_cpr_blocker(RAMBlock *rb);
>> +
>>   #endif
>>   #endif
>> diff --git a/include/exec/ramblock.h b/include/exec/ramblock.h
>> index 0babd10..64484cd 100644
>> --- a/include/exec/ramblock.h
>> +++ b/include/exec/ramblock.h
>> @@ -39,6 +39,7 @@ struct RAMBlock {
>>       /* RCU-enabled, writes protected by the ramlist lock */
>>       QLIST_ENTRY(RAMBlock) next;
>>       QLIST_HEAD(, RAMBlockNotifier) ramblock_notifiers;
>> +    Error *cpr_blocker;
>>       int fd;
>>       uint64_t fd_offset;
>>       int guest_memfd;
>> diff --git a/migration/savevm.c b/migration/savevm.c
>> index bc375db..85a3559 100644
>> --- a/migration/savevm.c
>> +++ b/migration/savevm.c
>> @@ -3315,12 +3315,14 @@ void vmstate_register_ram(MemoryRegion *mr, DeviceState *dev)
>>       qemu_ram_set_idstr(mr->ram_block,
>>                          memory_region_name(mr), dev);
>>       qemu_ram_set_migratable(mr->ram_block);
>> +    ram_block_add_cpr_blocker(mr->ram_block, &error_fatal);
>>   }
>>   void vmstate_unregister_ram(MemoryRegion *mr, DeviceState *dev)
>>   {
>>       qemu_ram_unset_idstr(mr->ram_block);
>>       qemu_ram_unset_migratable(mr->ram_block);
>> +    ram_block_del_cpr_blocker(mr->ram_block);
>>   }
>>   void vmstate_register_ram_global(MemoryRegion *mr)
>> diff --git a/system/physmem.c b/system/physmem.c
>> index 67c9db9..c416068 100644
>> --- a/system/physmem.c
>> +++ b/system/physmem.c
>> @@ -70,7 +70,10 @@
>>   #include "qemu/pmem.h"
>> +#include "qapi/qapi-types-migration.h"
>> +#include "migration/blocker.h"
>>   #include "migration/cpr.h"
>> +#include "migration/options.h"
>>   #include "migration/vmstate.h"
>>   #include "qemu/range.h"
>> @@ -1899,6 +1902,14 @@ static void ram_block_add(RAMBlock *new_block, Error **errp)
>>               qemu_mutex_unlock_ramlist();
>>               goto out_free;
>>           }
>> +
>> +        error_setg(&new_block->cpr_blocker,
>> +                   "Memory region %s uses guest_memfd, "
>> +                   "which is not supported with CPR.",
>> +                   memory_region_name(new_block->mr));
>> +        migrate_add_blocker_modes(&new_block->cpr_blocker, errp,
>> +                                  MIG_MODE_CPR_TRANSFER,
>> +                                  -1);
>>       }
>>       ram_size = (new_block->offset + new_block->max_length) >> TARGET_PAGE_BITS;
>> @@ -4059,3 +4070,60 @@ bool ram_block_discard_is_required(void)
>>       return qatomic_read(&ram_block_discard_required_cnt) ||
>>              qatomic_read(&ram_block_coordinated_discard_required_cnt);
>>   }
>> +
>> +/*
>> + * Return true if ram contents would be lost during CPR.  Do not exclude rom,
>> + * because the rom file could change in new QEMU.
>> + */
>> +static bool ram_is_volatile(RAMBlock *rb)
> 
> Can we call this
> 
> ram_is_cpr_compatible() / ram_is_cpr_incompatible() or sth. instead?
> 
> Talking about RAM and "volatile" is misleading, and the function is specific to CPR already (e.g., comment :) ).

Will do, thanks - steve




  reply	other threads:[~2025-02-15  1:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 20:12 [PATCH V2] migration: ram block cpr blockers Steve Sistare
2025-02-14 21:21 ` David Hildenbrand
2025-02-14 21:44   ` Steven Sistare [this message]
2025-02-18 17:27     ` Peter Xu

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=49c83982-46bf-4ab3-a683-776d4c342b27@oracle.com \
    --to=steven.sistare@oracle.com \
    --cc=david@redhat.com \
    --cc=farosas@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --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).