qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, qemu-devel@nongnu.org
Cc: Tom Musta <tommusta@gmail.com>, Paul Mackerras <paulus@samba.org>,
	qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-ppc: Add support for POWER8 pvr 0x4D0000
Date: Wed, 25 Jun 2014 12:58:06 +0200	[thread overview]
Message-ID: <53AAAB3E.1000007@suse.de> (raw)
In-Reply-To: <1403682110-29109-1-git-send-email-aik@ozlabs.ru>


On 25.06.14 09:41, Alexey Kardashevskiy wrote:
> At the moment QEMU knows about one version of POWER8 CPU with
> PVR 0x4B.0000. This CPU class is defined as "POWER8". The linux
> kernel names it as "POWER8E" which is different from the name QEMU uses.
>
> Now we get another version of POWER8 which is architecturally equivalent
> to POWER8E but has different PVR 0x4D.0000 so QEMU fails to find
> a PPC CPU class on these machines. The linux kernel names these CPUs as
> "POWER8".
>
> This renames the existing "POWER8" to "POWER8E" to be more precise and
> stay in sync with the linux kernel.
>
> This adds a new "POWER8" family which calls POWER8E class init function
> and defines own PVR mask (used to match a CPU class) and desc (used to
> create dynamic version-less CPU class).
>
> This does not change CPU class fw_name attribute as the host POWER8
> firmware keeps using "PowerPC,POWER8" on both POWER8 and POWER8E.
>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: Tom Musta <tommusta@gmail.com>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>

Thanks, applied to ppc-next.


Alex

      reply	other threads:[~2014-06-25 10:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  7:41 [Qemu-devel] [PATCH] target-ppc: Add support for POWER8 pvr 0x4D0000 Alexey Kardashevskiy
2014-06-25 10:58 ` 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=53AAAB3E.1000007@suse.de \
    --to=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=paulus@samba.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=tommusta@gmail.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).