From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Paolo Bonzini <pbonzini@redhat.com>, Alexander Graf <agraf@suse.de>
Cc: "Paul Mackerras" <paulus@samba.org>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"Nikunj A Dadhania" <nikunj@linux.vnet.ibm.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] spapr: add "compat" machine option
Date: Mon, 30 Sep 2013 22:57:50 +1000 [thread overview]
Message-ID: <5249754E.6070308@ozlabs.ru> (raw)
In-Reply-To: <52496601.6040500@redhat.com>
On 30.09.2013 21:52, Paolo Bonzini wrote:
> Il 30/09/2013 13:25, Alexander Graf ha scritto:
>> On 27.09.2013, at 10:06, Alexey Kardashevskiy wrote:
>>
>>>> To be able to boot on newer hardware that the software support,
>>>> PowerISA defines a logical PVR, one per every PowerISA specification
>>>> version from 2.04.
>>>>
>>>> This adds the "compat" option which takes values 205 or 206 and forces
>>>> QEMU to boot the guest with a logical PVR (CPU_POWERPC_LOGICAL_2_05 or
>>>> CPU_POWERPC_LOGICAL_2_06).
>>>>
>>>> The guest reads the logical PVR value from "cpu-version" property of
>>>> a CPU device node.
>>>>
>
> Why is the option under -machine instead of -cpu?
Because it is still the same CPU and the guest will still read the real
PVR from the hardware (which it may not support but this is why we need
compatibility mode).
It is possible to run QEMU with -cpu POWER8 with some old distro which
does not know about power8, it will switch to power6-compat mode, the
the user does "yum update" (or analog) and then the new kernel (with
power8 support) will do H_CAS again and this time "raw" power8 should be
selected.
--
With best regards
Alexey Kardashevskiy -- icq: 52150396
next prev parent reply other threads:[~2013-09-30 12:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 8:06 [Qemu-devel] [PATCH] spapr: add "compat" machine option Alexey Kardashevskiy
2013-09-30 11:25 ` Alexander Graf
2013-09-30 11:52 ` Paolo Bonzini
2013-09-30 12:57 ` Alexey Kardashevskiy [this message]
2013-11-05 9:06 ` Paolo Bonzini
2013-11-05 9:16 ` Alexander Graf
2013-11-05 9:52 ` Paolo Bonzini
2013-11-05 10:27 ` Alexander Graf
2013-11-05 10:33 ` Paolo Bonzini
2013-11-05 10:45 ` Alexey Kardashevskiy
2013-11-05 10:46 ` Paolo Bonzini
2013-11-05 13:53 ` Andreas Färber
2013-11-06 11:36 ` Igor Mammedov
2013-11-07 9:11 ` Alexey Kardashevskiy
2013-11-07 13:36 ` Igor Mammedov
2013-11-08 8:22 ` Alexey Kardashevskiy
2013-11-08 13:20 ` Andreas Färber
2013-11-08 14:57 ` Alexey Kardashevskiy
2013-11-08 15:07 ` Andreas Färber
2013-11-07 14:01 ` Andreas Färber
2013-11-08 8:22 ` [Qemu-devel] [PATCH v2 0/2] " Alexey Kardashevskiy
2013-11-08 8:22 ` [Qemu-devel] [PATCH v2 1/2] cpu: add suboptions support Alexey Kardashevskiy
2013-11-08 8:22 ` [Qemu-devel] [PATCH v2 2/2] target-ppc: add "compat" CPU option Alexey Kardashevskiy
2013-11-08 13:24 ` [Qemu-devel] [PATCH v2 0/2] spapr: add "compat" machine option Andreas Färber
2013-11-06 3:27 ` [Qemu-devel] [PATCH] " Paul Mackerras
2013-09-30 13:22 ` Alexey Kardashevskiy
2013-09-30 14:49 ` Alexander Graf
2013-11-05 2:19 ` Alexey Kardashevskiy
2013-11-05 9:23 ` Alexander Graf
2013-11-06 5:48 ` Paul Mackerras
2013-11-06 12:07 ` Alexander Graf
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=5249754E.6070308@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=nikunj@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--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 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.