qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Cc: agraf@suse.de, qemu-devel@nongnu.org,
	Alexey Kardashevskiy <aik@ozlabs.ru>
Subject: [Qemu-devel] [PATCH 0/5] ppc: Improve sPAPR CPU compatibility mode settings
Date: Tue,  7 Jun 2016 17:39:35 +0200	[thread overview]
Message-ID: <1465313980-31281-1-git-send-email-thuth@redhat.com> (raw)

If a guest currently only requests PowerISA 2.07 compatiblity mode with
the "ibm,client-architecture-support" firmware call, but does not
specify a matching real PVR for the host CPU on a POWER8 host,
it ends up in POWER7 / PowerISA 2.06 compatibility mode since QEMU
does not support 2.07 compatibility mode yet. This currently happens
when running a Linux guest on a POWER8NVL host, since Linux guests
do not use the PVR for these CPUs for the "ibm,client-architecture-
support" call yet (but I submitted a patch for the kernel to fix this
issue there last week, so the support should soon be there, too).

Anyway, QEMU should also support a proper 2.07 compatibility mode
if the host CPU can do it. So this patch series introduces such a
mode and does some clean-ups and other fixes along the way (e.g.
it splits the ambiguous pcr_mask setting into two variables, one
for defining the valid bits in the PCR register, and one for
storing the valid ISA levels).

Thomas Huth (5):
  ppc/spapr: Refactor h_client_architecture_support() CPU parsing code
  ppc: Split pcr_mask settings into supported bits and the register mask
  ppc: Provide function to get CPU class of the host CPU
  ppc: Improve PCR bit selection in ppc_set_compat()
  ppc: Add PowerISA 2.07 compatibility mode

 hw/ppc/spapr_hcall.c        | 63 +++++++++++++++++++++++++++------------------
 target-ppc/cpu-qom.h        |  3 ++-
 target-ppc/cpu.h            |  1 +
 target-ppc/kvm.c            | 19 ++++++++++----
 target-ppc/kvm_ppc.h        |  7 +++++
 target-ppc/translate_init.c | 22 +++++++++++-----
 6 files changed, 78 insertions(+), 37 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2016-06-07 15:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 15:39 Thomas Huth [this message]
2016-06-07 15:39 ` [Qemu-devel] [PATCH 1/5] ppc/spapr: Refactor h_client_architecture_support() CPU parsing code Thomas Huth
2016-06-08  0:33   ` Michael Roth
2016-06-07 15:39 ` [Qemu-devel] [PATCH 2/5] ppc: Split pcr_mask settings into supported bits and the register mask Thomas Huth
2016-06-08  0:34   ` Michael Roth
2016-06-07 15:39 ` [Qemu-devel] [PATCH 3/5] ppc: Provide function to get CPU class of the host CPU Thomas Huth
2016-06-08  0:38   ` Michael Roth
2016-06-07 15:39 ` [Qemu-devel] [PATCH 4/5] ppc: Improve PCR bit selection in ppc_set_compat() Thomas Huth
2016-06-08  1:12   ` David Gibson
2016-06-08  6:47     ` Thomas Huth
2016-06-08  5:44   ` [Qemu-devel] [Qemu-ppc] " David Gibson
2016-06-08  6:59     ` Thomas Huth
2016-06-08  7:24       ` David Gibson
2016-06-08  7:37         ` Thomas Huth
2016-06-07 15:39 ` [Qemu-devel] [PATCH 5/5] ppc: Add PowerISA 2.07 compatibility mode Thomas Huth
2016-06-08  1:11 ` [Qemu-devel] [PATCH 0/5] ppc: Improve sPAPR CPU compatibility mode settings 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=1465313980-31281-1-git-send-email-thuth@redhat.com \
    --to=thuth@redhat.com \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).