From: Alexander Graf <agraf@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Cleanup machine naming conventions, and prepare for 2.2 release
Date: Mon, 08 Sep 2014 13:39:37 +0200 [thread overview]
Message-ID: <540D9579.9060803@suse.de> (raw)
In-Reply-To: <1410154231-19828-1-git-send-email-david@gibson.dropbear.id.au>
On 08.09.14 07:30, David Gibson wrote:
> 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.
>
> However, these are organized a bit differently from those for PC: on PC,
> the default plain "pc" machine type is just an alias for the most recent
> versioned machine type. In sPAPR, 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. Since qemu-2.1 is now released, we also
> create a new pseries-2.2 machine type, to incorporate changes during this
> development cycle (for now it is identical to pseries-2.1).
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Thanks, applied to ppc-next.
Alex
prev parent reply other threads:[~2014-09-08 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 5:30 [Qemu-devel] [PATCH] spapr: Cleanup machine naming conventions, and prepare for 2.2 release David Gibson
2014-09-08 11:39 ` Alexander Graf [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=540D9579.9060803@suse.de \
--to=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--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).