From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: qemu-devel@nongnu.org, qemu-rust@nongnu.org
Subject: Re: [PATCH 08/11] rust: qemu-macros: add ToMigrationState derive macro
Date: Tue, 4 Nov 2025 15:40:47 +0100 [thread overview]
Message-ID: <21c1ea17-6555-4dbf-b10d-e62eca302acf@redhat.com> (raw)
In-Reply-To: <aQjPApAmM2Hma3Rm@intel.com>
On 11/3/25 16:49, Zhao Liu wrote:
>> did you miss something like the following?
>>
>>
>> diff --git a/rust/qemu-macros/src/migration_state.rs b/rust/qemu-macros/src/migration_state.rs
>> index 5edf0efe687f..2064bb73a6f0 100644
>> --- a/rust/qemu-macros/src/migration_state.rs
>> +++ b/rust/qemu-macros/src/migration_state.rs
>> @@ -236,6 +236,16 @@ pub struct #name {
>> }
>> }
>>
>> + fn generate_vmstate_impl(&self) -> TokenStream {
>> + let name = self.migration_state_name();
>> +
>> + quote! {
>> + unsafe impl ::migration::VMState for #name {
>> + const BASE: ::migration::VMStateField = ::common::Zeroable::ZERO;
>
> It seems the generated migration_state_struct needs a complete VMSD:
> collect all its fields and build a VMSD.
>
> And then apply impl_vmstate_struct! to this migration_state_struct.
>
> If we zero the BASE, then `vmstate_of!(Self, migration_state)` seems
> can't migrate its fields.
The VMStateDescription for the inner struct is indeed missing, but you
need to write it yourself and apply impl_vmstate_struct, because the
derive macro cannot know the checks or version_ids for each field, or
the subsections.
The VMStateDescription for Migratable<> however is automatic (of
course), and the outer VMStateDescription for the device is simple---it
consists only of the parent class if applicable, and the Migratable<>,
similar to VMSTATE_PL011.
For HPET, you'll have to move the subsections from VMSTATE_HPET to the
inner VMState.
Paolo
next prev parent reply other threads:[~2025-11-04 14:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251001075005.1041833-1-pbonzini@redhat.com>
2025-10-01 8:00 ` [PATCH preview 00/14] rust: QObject and QAPI bindings Paolo Bonzini
2025-10-01 8:00 ` [PATCH 01/14] qobject: make refcount atomic Paolo Bonzini
2025-10-13 7:51 ` Zhao Liu
2025-10-01 8:00 ` [PATCH 02/14] rust: add basic QObject bindings Paolo Bonzini
2025-10-01 8:00 ` [PATCH 03/14] subprojects: add serde Paolo Bonzini
2025-10-01 8:00 ` [PATCH 04/14] rust: add Serialize implementation for QObject Paolo Bonzini
2025-10-01 8:00 ` [PATCH 05/14] rust: add Serializer (to_qobject) " Paolo Bonzini
2025-10-01 8:00 ` [PATCH 06/14] rust: add Deserialize " Paolo Bonzini
2025-10-01 8:00 ` [PATCH 07/14] rust: add Deserializer (from_qobject) " Paolo Bonzini
2025-10-01 8:00 ` [PATCH 08/14] rust/qobject: add Display/Debug Paolo Bonzini
2025-10-01 8:00 ` [PATCH 09/14] scripts/qapi: add QAPISchemaIfCond.rsgen() Paolo Bonzini
2025-10-01 8:00 ` [PATCH 10/14] scripts/qapi: generate high-level Rust bindings Paolo Bonzini
2025-10-01 8:00 ` [PATCH 11/14] scripts/qapi: strip trailing whitespaces Paolo Bonzini
2025-10-01 8:00 ` [PATCH 12/14] scripts/rustc_args: add --no-strict-cfg Paolo Bonzini
2025-10-01 8:00 ` [PATCH 13/14] rust/util: build QAPI types Paolo Bonzini
2025-10-01 8:00 ` [PATCH 14/14] rust: start qapi tests Paolo Bonzini
[not found] ` <20251001075210.1042479-8-pbonzini@redhat.com>
2025-11-03 10:25 ` [PATCH 08/11] rust: qemu-macros: add ToMigrationState derive macro Zhao Liu
2025-11-03 15:49 ` Zhao Liu
2025-11-04 14:40 ` Paolo Bonzini [this message]
2025-11-04 14:41 ` Zhao Liu
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=21c1ea17-6555-4dbf-b10d-e62eca302acf@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.org \
--cc=zhao1.liu@intel.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).