From: Gerd Hoffmann <kraxel@redhat.com>
To: Igor Mitsyanko <i.mitsyanko@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Andreas <afaerber@suse.de>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 2/2] hw/arm_gic_common: Use vmstate struct rather than save/load functions
Date: Tue, 19 Mar 2013 08:14:47 +0100 [thread overview]
Message-ID: <51481067.3080007@redhat.com> (raw)
In-Reply-To: <CA+x0pt6QQ+JCAiYvSPecvuLa22pP5pn+C5rgmzvSMvwPz6Ajbg@mail.gmail.com>
Hi,
>> (vmstate.h is getting hugely repetitive to the point that I'm
>> really tempted to say we should just autogenerate it. That way
>> you could define a fairly small set of things (arrays, base types,
>> safe vs unsafe, etc) and have a script generate the cross product,
>> rather than the current setup where there is a lot of hand written
>> repetition and a tendency to gaps in the coverage where nobody's
>> using them yet.)
> I can recall a qemu-devel discussion over a long-term QOM goals a while
> ago.Somebody suggested that in the future we will define devices state
> structures using some special macro which will be parsed during
> compilation, serializing each member for both QOM introspection and vmstate
> migration.
That is where I see the future too. Michael Roth [ cc'ed ] has this on
his agenda. We have code generation infrastructure for qapi and it
surely makes sense to reuse that for vmstate.
cheers,
Gerd
next prev parent reply other threads:[~2013-03-19 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 17:47 [Qemu-devel] [PATCH v2 0/2] arm_gic: convert to vmstate Peter Maydell
2013-03-18 17:47 ` [Qemu-devel] [PATCH v2 1/2] arm_gic: Fix sizes of state fields in preparation for vmstate support Peter Maydell
[not found] ` <51476E81.8000904@gmail.com>
2013-03-18 19:46 ` Igor Mitsyanko
2013-03-19 10:53 ` Andreas Färber
2013-03-18 17:47 ` [Qemu-devel] [PATCH v2 2/2] hw/arm_gic_common: Use vmstate struct rather than save/load functions Peter Maydell
[not found] ` <51476DD1.6070705@gmail.com>
2013-03-18 19:48 ` Igor Mitsyanko
2013-03-18 20:20 ` Peter Maydell
2013-03-18 20:43 ` Igor Mitsyanko
2013-03-19 7:14 ` Gerd Hoffmann [this message]
2013-03-19 10:57 ` Andreas Färber
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=51481067.3080007@redhat.com \
--to=kraxel@redhat.com \
--cc=afaerber@suse.de \
--cc=i.mitsyanko@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=patches@linaro.org \
--cc=peter.maydell@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).