From: Steven Sistare <steven.sistare@oracle.com>
To: Fabiano Rosas <farosas@suse.de>, qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>,
David Hildenbrand <david@redhat.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Michael Roth <michael.roth@amd.com>
Subject: Re: [PATCH V1] migration: cpr breaks SNP guest
Date: Thu, 27 Mar 2025 10:46:18 -0400 [thread overview]
Message-ID: <0ecbc966-fdbe-48d8-ac3f-401d0f0565a6@oracle.com> (raw)
In-Reply-To: <87iknua70n.fsf@suse.de>
On 3/27/2025 10:21 AM, Fabiano Rosas wrote:
> Steve Sistare <steven.sistare@oracle.com> writes:
>
>> With aux-ram-share=off, booting an SNP guest fails with:
>>
>> ../util/error.c:68: error_setv: Assertion `*errp == NULL' failed.
>>
>> This is because a CPR blocker for the guest_memfd ramblock is added
>> twice, once in ram_block_add_cpr_blocker because aux-ram-share=off so
>> rb->fd < 0, and once in ram_block_add for a specific guest_memfd blocker.
>>
>> To fix, add the guest_memfd blocker iff a generic one would not be
>> added by ram_block_add_cpr_blocker.
>>
>> Fixes: 094a3dbc55df ("migration: ram block cpr blockers")
>> Reported-by: Tom Lendacky <thomas.lendacky@amd.com>
>> Reported-by: Michael Roth <michael.roth@amd.com>
>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
>> ---
>> system/physmem.c | 19 ++++++++++++-------
>> 1 file changed, 12 insertions(+), 7 deletions(-)
>>
>> diff --git a/system/physmem.c b/system/physmem.c
>> index e97de3e..cfafb06 100644
>> --- a/system/physmem.c
>> +++ b/system/physmem.c
>> @@ -1908,13 +1908,18 @@ static void ram_block_add(RAMBlock *new_block, Error **errp)
>> 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);
>> + /*
>> + * Add a specific guest_memfd blocker if a generic one would not be
>> + * added by ram_block_add_cpr_blocker.
>> + */
>> + if (new_block->fd >= 0 && qemu_ram_is_shared(new_block)) {
>
> Can we avoid having two instances of the same condition that will need
> to be kept in sync? What about:
>
> /*
> * Preserving guest_memfd may be sufficient for CPR, but it has not
> * been tested yet.
> */
> if (ram_is_cpr_compatible(new_block)) {
> ...
>
Sure, that is better. I will send V2 shortly.
- Steve
>> + 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;
prev parent reply other threads:[~2025-03-27 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 13:36 [PATCH V1] migration: cpr breaks SNP guest Steve Sistare
2025-03-27 14:10 ` Tom Lendacky
2025-03-27 14:21 ` Fabiano Rosas
2025-03-27 14:46 ` Steven Sistare [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=0ecbc966-fdbe-48d8-ac3f-401d0f0565a6@oracle.com \
--to=steven.sistare@oracle.com \
--cc=david@redhat.com \
--cc=farosas@suse.de \
--cc=michael.roth@amd.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.lendacky@amd.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).