All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Thomas Huth <thuth@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org, abologna@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.7 0/5] spapr: Fix regression in CPU alias handling
Date: Tue, 9 Aug 2016 21:09:53 +0530	[thread overview]
Message-ID: <20160809153953.GC3027@in.ibm.com> (raw)
In-Reply-To: <1470734229-10832-1-git-send-email-thuth@redhat.com>

On Tue, Aug 09, 2016 at 11:17:04AM +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.

I believed that "-cpu POWER8" on POWER8E host was broken in a way as
the guest CPUs were getting reported as POWER8E instead of POWER8

(/proc/cpuinfo of guest)
cpu		: POWER8E (raw), altivec supported

I thought, the correct configuration should have been

cpu             : POWER8 (architected), altivec supported

which is what you get when you use POWER8 in compat mode on
POWER8E host like below:

-cpu host -global driver=host-powerpc64-cpu,property=compat,value=power8

However as you note libvirt is dependent on supporting POWER8 and
there have been discussions and conclusions on this earlier, I guess
it is better now to have your patchset to restore the expectations of
libvirt.

Regards,
Bharata.

  parent reply	other threads:[~2016-08-09 15:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09  9:17 [Qemu-devel] [PATCH for-2.7 0/5] spapr: Fix regression in CPU alias handling Thomas Huth
2016-08-09  9:17 ` [Qemu-devel] [PATCH 1/5] ppc: Introduce a function to look up CPU alias strings Thomas Huth
2016-08-09  9:17 ` [Qemu-devel] [PATCH 2/5] hw/ppc/spapr: Look up CPU alias names instead of hard-coding the aliases Thomas Huth
2016-08-09  9:17 ` [Qemu-devel] [PATCH 3/5] hw/ppc/spapr: Do not leak the memory of the type string Thomas Huth
2016-08-09  9:17 ` [Qemu-devel] [PATCH 4/5] ppc/kvm: Do not mess up the generic CPU family registration Thomas Huth
2016-08-09  9:17 ` [Qemu-devel] [PATCH 5/5] ppc/kvm: Register also a generic spapr CPU core family type Thomas Huth
2016-08-09 11:27 ` [Qemu-devel] [PATCH for-2.7 0/5] spapr: Fix regression in CPU alias handling Andrea Bolognani
2016-08-09 15:39 ` Bharata B Rao [this message]
2016-08-09 16:22   ` Thomas Huth
2016-08-09 16:37     ` Andrea Bolognani
2016-08-09 15:56 ` Thomas Huth

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=20160809153953.GC3027@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=abologna@redhat.com \
    --cc=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.