From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org,
Alexander Mikhalitsyn <alexander@mihalicyn.com>,
Juraj Marcin <jmarcin@redhat.com>
Subject: Re: [RFC PATCH v1 00/17] migration: vmstate_save|load changes for peterx
Date: Wed, 25 Mar 2026 17:10:51 -0300 [thread overview]
Message-ID: <87mrzvk6us.fsf@suse.de> (raw)
In-Reply-To: <acQ61yMtzZPfLUAj@x1.local>
Peter Xu <peterx@redhat.com> writes:
> On Tue, Mar 24, 2026 at 04:43:15PM -0300, Fabiano Rosas wrote:
>> Too much stuff to mention inline on the series, here's some patches on
>> top. Let me know what you think! Feel free to drop it all or
>> incorporate or whatever.
>>
>> Based-on: [PATCH RFC 00/10] vmstate: Implement VMS_ARRAY_OF_POINTER_AUTO_ALLOC
>> 20260317232332.15209-1-peterx@redhat.com
>> https://lore.kernel.org/r/20260317232332.15209-1-peterx@redhat.com
>>
>> which is in turn based on https://gitlab.com/farosas/qemu/-/commits/migration-staging
>>
>> I pushed it all to https://gitlab.com/farosas/qemu/-/commits/migration-rfc-auto-alloc
>>
>> CI run: https://gitlab.com/farosas/qemu/-/pipelines/2406278684
>>
>> Fabiano Rosas (17):
>> vmstate: fixup the use of AUTO_ALLOC flag
>> vmstate: Remove vmstate_use_marker_field
>> vmstate: Stop checking size for nullptr compression
>> vmstate: Set error inside of vmstate_save_field_with_vmdesc
>> vmstate: Remove vmdesc_loop
>> vmstate: Put array of pointers code together
>> vmstate: Create and save ptr marker in same function
>> vmstate: Don't recompute size and n_elems in vmstate_size
>> vmstate: Increase scope of vmstate_handle_alloc
>> vmstate: Remove curr_elem_p
>> vmstate: Introduce vmstate_first
>> vmstate: Introduce vmstate_next
>> vmstate: Drop VMS_ARRAY_OF_POINTER_AUTO_ALLOC
>> vmstate: Move VMS_MUST_EXIST check
>> vmstate: Invert exists check
>> vmstate: Declare variables at the top
>> vmstate: Reduce indentation levels
>
> Considering that this prior series may block the nvme series, I'll be
> slightly conservative on what to collect, but I'll collect as much as I can
> that makes me still feel confident when I repost; we'll see.
>
Sure, if there's anything you still find valuable but won't take for the
repost let me know and I can send a separate series on top if that's the
case.
prev parent reply other threads:[~2026-03-25 20:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 19:43 [RFC PATCH v1 00/17] migration: vmstate_save|load changes for peterx Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 01/17] vmstate: fixup the use of AUTO_ALLOC flag Fabiano Rosas
2026-03-25 16:18 ` Peter Xu
2026-03-24 19:43 ` [RFC PATCH v1 02/17] vmstate: Remove vmstate_use_marker_field Fabiano Rosas
2026-03-25 16:37 ` Peter Xu
2026-03-25 17:51 ` Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 03/17] vmstate: Stop checking size for nullptr compression Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 04/17] vmstate: Set error inside of vmstate_save_field_with_vmdesc Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 05/17] vmstate: Remove vmdesc_loop Fabiano Rosas
2026-03-25 17:07 ` Peter Xu
2026-03-25 18:11 ` Fabiano Rosas
2026-03-25 21:43 ` Peter Xu
2026-03-24 19:43 ` [RFC PATCH v1 06/17] vmstate: Put array of pointers code together Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 07/17] vmstate: Create and save ptr marker in same function Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 08/17] vmstate: Don't recompute size and n_elems in vmstate_size Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 09/17] vmstate: Increase scope of vmstate_handle_alloc Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 10/17] vmstate: Remove curr_elem_p Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 11/17] vmstate: Introduce vmstate_first Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 12/17] vmstate: Introduce vmstate_next Fabiano Rosas
2026-03-26 14:18 ` Peter Xu
2026-03-24 19:43 ` [RFC PATCH v1 13/17] vmstate: Drop VMS_ARRAY_OF_POINTER_AUTO_ALLOC Fabiano Rosas
2026-03-25 19:29 ` Peter Xu
2026-03-25 21:49 ` Peter Xu
2026-03-25 21:57 ` Peter Xu
2026-03-24 19:43 ` [RFC PATCH v1 14/17] vmstate: Move VMS_MUST_EXIST check Fabiano Rosas
2026-03-25 19:38 ` Peter Xu
2026-03-24 19:43 ` [RFC PATCH v1 15/17] vmstate: Invert exists check Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 16/17] vmstate: Declare variables at the top Fabiano Rosas
2026-03-24 19:43 ` [RFC PATCH v1 17/17] vmstate: Reduce indentation levels Fabiano Rosas
2026-03-25 19:43 ` [RFC PATCH v1 00/17] migration: vmstate_save|load changes for peterx Peter Xu
2026-03-25 20:10 ` Fabiano Rosas [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=87mrzvk6us.fsf@suse.de \
--to=farosas@suse.de \
--cc=alexander@mihalicyn.com \
--cc=jmarcin@redhat.com \
--cc=peterx@redhat.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