From: David Gibson <david@gibson.dropbear.id.au>
To: Markus Armbruster <armbru@redhat.com>
Cc: aik@ozlabs.ru, agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Make machine naming conventions closer to those for PC
Date: Thu, 14 Aug 2014 13:10:30 +1000 [thread overview]
Message-ID: <20140814031029.GI7628@voom.redhat.com> (raw)
In-Reply-To: <87tx5g3als.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 3198 bytes --]
On Wed, Aug 13, 2014 at 01:14:23PM +0200, Markus Armbruster wrote:
> David Gibson <david@gibson.dropbear.id.au> writes:
>
> > As of qemu-2.1, spapr/pseries, has a set of versioned machine classes to
> > represent the machine type as it appeared to the guest in different qemu
> > versions. This allows for safe migration of guests between current and
> > future qemu versions.
> >
> > In PC, however, the default plain "pc" machine type is just an alias for
> > the most recent versioned machine type. In sPAPR at the moment, it names
> > the base machine class from which the versioned types are derived.
> >
> > The PC approach is preferable; it makes it clearer which explicit version
> > is the current one. Additionally updating the "current" machine as the
> > base class makes it even more likely than otherwise to incorrectly alter
> > the versioned machines' behaviour when updating the current machine.
> >
> > Therefore this patch changes sPAPR to the PC approach - the base class
> > becomes abstract, and plain "pseries" becomes an alias for the most
> > recent versioned machine class.
> >
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > ---
> > hw/ppc/spapr.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> > index d01978f..2785dbc 100644
> > --- a/hw/ppc/spapr.c
> > +++ b/hw/ppc/spapr.c
> > @@ -1583,7 +1583,6 @@ static void spapr_machine_class_init(ObjectClass *oc, void *data)
> >
> > mc->name = "pseries";
> > mc->desc = "pSeries Logical Partition (PAPR compliant)";
> > - mc->is_default = 1;
> > mc->init = ppc_spapr_init;
> > mc->reset = ppc_spapr_reset;
> > mc->block_default_type = IF_SCSI;
>
> I suspect many of these assignments are actually overwritten by the
> derived machine types' class init function. Without that, mc->name =
> "pseries" would clash with the mc->alias = "pseries" below, wouldn't
> i?
Less than you'd think, since there's basically only one derived
machine type variant so far.
mc->name does need to change though, I'll rework.
> Care to trim the redundant assignments?
>
> > @@ -1598,6 +1597,7 @@ static void spapr_machine_class_init(ObjectClass *oc, void *data)
> > static const TypeInfo spapr_machine_info = {
> > .name = TYPE_SPAPR_MACHINE,
> > .parent = TYPE_MACHINE,
> > + .abstract = true,
> > .instance_size = sizeof(sPAPRMachineState),
> > .instance_init = spapr_machine_initfn,
> > .class_init = spapr_machine_class_init,
> > @@ -1613,7 +1613,8 @@ static void spapr_machine_2_1_class_init(ObjectClass *oc, void *data)
> >
> > mc->name = "pseries-2.1";
> > mc->desc = "pSeries Logical Partition (PAPR compliant) v2.1";
> > - mc->is_default = 0;
> > + mc->alias = "pseries";
> > + mc->is_default = 1;
> > }
> >
> > static const TypeInfo spapr_machine_2_1_info = {
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-14 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 1:23 [Qemu-devel] [PATCH] spapr: Make machine naming conventions closer to those for PC David Gibson
2014-08-13 11:14 ` Markus Armbruster
2014-08-14 3:10 ` David Gibson [this message]
2014-08-13 13:10 ` Andreas Färber
2014-08-14 5:55 ` David Gibson
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=20140814031029.GI7628@voom.redhat.com \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=armbru@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;
as well as URLs for NNTP newsgroup(s).