qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Juan Quintela <quintela@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [RFC for-next 0/2] QOM VMStateDescription remix
Date: Mon, 02 Sep 2013 13:28:30 +0200	[thread overview]
Message-ID: <5224765E.8090005@suse.de> (raw)
In-Reply-To: <1375063438-3149-1-git-send-email-afaerber@suse.de>

Am 29.07.2013 04:03, schrieb Andreas Färber:
> Hello,
> 
> Based on a comment from mst, this mini-series proposes to change semantics of
> VMStateDescription registration to be more similar to those of static properties.
> 
> Today, a device has one VMStateDescription, the last assignment to dc->vmsd wins.
> This means that a device must take care to include state of its parent type.
> To avoid dealing with individual fields, VMSTATE_STRUCT() and wrappers have
> been used. Such fields often require access of the deprecated QOM parent field.
> 
> The proposal is that, e.g., TYPE_CPU assigns its own VMStateDescription and
> derived types (e.g., TYPE_ALPHA_CPU) register a VMStateDescription with name
> and versions to be used and only the fields specific to that type.
> In this v1, versions of the parents' vmsd are ignored, so someone changing CPU's
> DeviceClass::vmsd (as opposed to DeviceClass::vmsd->fields[0].vmsd) would need
> to assure appropriate .field_exists tests or bump the version of derived types'
> vmsd as if a field had been added there.

Ping?

Andreas

> 
> Only rudimentarily tested: I've run some machines that didn't crash on startup.
> 
> Regards,
> Andreas
> 
> Cc: Michael S. Tsirkin <mst@redhat.com>
> Cc: Juan Quintela <quintela@redhat.com>
> Cc: Anthony Liguori <anthony@codemonkey.ws>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> 
> Andreas Färber (2):
>   qdev: Construct VMStateDescription from type hierarchy
>   cpu: Move VMSTATE_CPU() into TYPE_CPU VMStateDescription
> 
>  hw/core/qdev.c            | 102 +++++++++++++++++++++++++++++++++++++++++-----
>  include/hw/qdev-core.h    |   1 +
>  include/qom/cpu.h         |   4 --
>  qom/cpu.c                 |  10 +++++
>  stubs/vmstate.c           |   1 +
>  target-alpha/machine.c    |   1 -
>  target-openrisc/machine.c |   1 -
>  7 files changed, 103 insertions(+), 17 deletions(-)
> 


-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2013-09-02 11:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  2:03 [Qemu-devel] [RFC for-next 0/2] QOM VMStateDescription remix Andreas Färber
2013-07-29  2:03 ` [Qemu-devel] [RFC for-next 1/2] qdev: Construct VMStateDescription from type hierarchy Andreas Färber
2013-07-29  2:03 ` [Qemu-devel] [RFC for-next 2/2] cpu: Move VMSTATE_CPU() into TYPE_CPU VMStateDescription Andreas Färber
2013-07-29  4:30   ` Jia Liu
2013-09-02 11:28 ` Andreas Färber [this message]
2013-09-02 11:41 ` [Qemu-devel] [RFC for-next 0/2] QOM VMStateDescription remix Michael S. Tsirkin
2014-02-07 21:28   ` Andreas Färber
2014-02-07 21:39     ` Peter Maydell

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=5224765E.8090005@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).