From: David Gibson <david@gibson.dropbear.id.au>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org, abologna@redhat.com,
bharata@linux.vnet.ibm.com, clg@kaod.org
Subject: Re: [Qemu-devel] [PATCH v2 0/5] spapr: Fix regression in CPU alias handling
Date: Wed, 10 Aug 2016 13:14:47 +1000 [thread overview]
Message-ID: <20160810031447.GI9057@voom.fritz.box> (raw)
In-Reply-To: <1470762001-414-1-git-send-email-thuth@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2626 bytes --]
On Tue, Aug 09, 2016 at 06:59:56PM +0200, Thomas Huth wrote:
> There is a regression with the "-cpu" parameter which has been
> introduced by the spapr CPU hotplug code: We used to allow to specify
> a "CPU family" name with the "-cpu" parameter when running on KVM so
> that the user does not need to know the gory details of the exact
> CPU version of the host CPU. For example, it was possible to
> use "-cpu POWER8" on a POWER8E host CPU. This behavior does not
> work anymore with the new hot-pluggable spapr-cpu-core types.
> Since libvirt already heavily depends on the old behavior, this
> is quite a severe regression in the QEMU parameter interface, thus
> I think these patches should still go into 2.7 if possible, to avoid
> that we break the "upper layers" with the final 2.7 release.
>
> This patch series fixes the regression (and two more minor bugs)
> by registering a family type for the spapr-cpu-core type, too
> (see the last patch). However, since that name clashes with the
> alias types that have been defined in spapr_cpu_core.c, we first
> have to introduce there a better way to handle CPU aliases (see
> the first two patches).
> The third patch fixes a small memory leak along the way, and
> the fourth patch makes sure that we do not mess up the generic
> CPU family type registration anymore (which was another regression
> introduced with the spapr CPU hotplug code).
>
> Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1363812
Applied to ppc-for-2.7, thanks.
>
> v2:
> - Add the "remove extra type variable" patch from Cédric Le Goater.
> - Remove the "Do not leak the memory of the type string" patch
> since it got obsoleted by Cédric's patch
>
> Cédric Le Goater (1):
> spapr: remove extra type variable
>
> Thomas Huth (4):
> ppc: Introduce a function to look up CPU alias strings
> hw/ppc/spapr: Look up CPU alias names instead of hard-coding the
> aliases
> ppc/kvm: Do not mess up the generic CPU family registration
> ppc/kvm: Register also a generic spapr CPU core family type
>
> hw/ppc/spapr.c | 15 ++++++---------
> hw/ppc/spapr_cpu_core.c | 38 +++++++++++++++++++++-----------------
> target-ppc/cpu.h | 1 +
> target-ppc/kvm.c | 19 +++++++++++--------
> target-ppc/translate_init.c | 13 +++++++++++++
> 5 files changed, 52 insertions(+), 34 deletions(-)
>
--
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-08-10 4:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 16:59 [Qemu-devel] [PATCH v2 0/5] spapr: Fix regression in CPU alias handling Thomas Huth
2016-08-09 16:59 ` [Qemu-devel] [PATCH v2 1/5] spapr: remove extra type variable Thomas Huth
2016-08-09 16:59 ` [Qemu-devel] [PATCH v2 2/5] ppc: Introduce a function to look up CPU alias strings Thomas Huth
2016-08-09 16:59 ` [Qemu-devel] [PATCH v2 3/5] hw/ppc/spapr: Look up CPU alias names instead of hard-coding the aliases Thomas Huth
2016-08-10 8:26 ` Cédric Le Goater
2016-08-09 17:00 ` [Qemu-devel] [PATCH v2 4/5] ppc/kvm: Do not mess up the generic CPU family registration Thomas Huth
2016-08-09 17:00 ` [Qemu-devel] [PATCH v2 5/5] ppc/kvm: Register also a generic spapr CPU core family type Thomas Huth
2016-08-10 3:14 ` David Gibson [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=20160810031447.GI9057@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=abologna@redhat.com \
--cc=agraf@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@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).