ppc/kvm: Register also a generic spapr CPU core family type
commitd11b268e1765e8878c1150d463b9f6dc3a8d4456
authorThomas Huth <thuth@redhat.com>
Tue, 9 Aug 2016 17:00:01 +0000 (9 19:00 +0200)
committerDavid Gibson <david@gibson.dropbear.id.au>
Wed, 10 Aug 2016 03:12:20 +0000 (10 13:12 +1000)
treeea7b8cf01e2fbe97664b8e0d224bd011c8347fc6
parent9c83fc2e8e1630e4d0fb10055563844b6e2cf2e0
ppc/kvm: Register also a generic spapr CPU core family type

There is a regression with the "-cpu" parameter 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.
Let's fix it by supporting a CPU family type for the spapr-cpu-core
on KVM, too.

Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1363812
Signed-off-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
target-ppc/kvm.c