From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Greg Kurz <groug@kaod.org>,
aik@ozlabs.ru, mdroth@linux.vnet.ibm.com,
nikunj@linux.vnet.ibm.com, agraf@suse.de, abologna@redhat.com,
armbru@redhat.com, qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
quintela@redhat.com, dgilbert@redhat.com, sursingh@redhat.com,
sbobroff@redhat.com
Subject: Re: [Qemu-devel] [PATCHv4 0/5] Clean up compatibility mode handling
Date: Fri, 2 Jun 2017 11:55:09 +1000 [thread overview]
Message-ID: <20170602015509.GG13397@umbus.fritz.box> (raw)
In-Reply-To: <f353022f-6b48-ab18-f156-bd8fac8cf884@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
On Thu, Jun 01, 2017 at 01:59:14PM +0200, Cédric Le Goater wrote:
> On 06/01/2017 08:52 AM, David Gibson wrote:
> > On Wed, May 31, 2017 at 10:58:57AM +0200, Greg Kurz wrote:
> >> On Wed, 31 May 2017 12:57:48 +1000
> >> David Gibson <david@gibson.dropbear.id.au> wrote:
> >>> [...]
> >>>> All old non-pseries machine types already complain when started with
> >>>> a POWER7 or newer CPU. Providing the extra error message looks weird:
> >>>>
> >>>> qemu-system-ppc64 -machine ppce500 \
> >>>> -cpu POWER7,compat=power6
> >>>> qemu-system-ppc64: CPU 'compat' property is deprecated and has no effect;
> >>>> use max-cpu-compat machine property instead
> >>>> MMU model 983043 not supported by this machine.
> >>>>
> >>>> but I guess it's better than crashing. :)
> >>>
> >>> Well, sure POWER7 doesn't make sense for an e500 machine for other
> >>> reasons. But POWER7 or POWER8 _would_ make sense for powernv, where
> >>> compat= doesn't.
> >>>
> >>
> >> The powernv machine type doesn't even support CPU features at all:
> >>
> >> chip_typename = g_strdup_printf(TYPE_PNV_CHIP "-%s", machine->cpu_model);
> >> if (!object_class_by_name(chip_typename)) {
> >> error_report("invalid CPU model '%s' for %s machine",
> >> machine->cpu_model, MACHINE_GET_CLASS(machine)->name);
> >> exit(1);
> >> }
> >
> > Ah, well, that's another bug, but not one that's in scope for this
> > series.
>
> PowerNV is still work in progress. I would not worry about it too much.
I wasn't intending to :).
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-06-02 2:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 5:23 [Qemu-devel] [PATCHv4 0/5] Clean up compatibility mode handling David Gibson
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 1/5] qapi: add explicit null to string input and output visitors David Gibson
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 2/5] migration: Mark CPU states dirty before incoming migration/loadvm David Gibson
2017-05-29 20:46 ` Greg Kurz
2017-05-30 6:15 ` David Gibson
2017-05-30 9:14 ` Dr. David Alan Gilbert
2017-05-30 13:03 ` Juan Quintela
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 3/5] pseries: Move CPU compatibility property to machine David Gibson
2017-06-01 5:44 ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh
2017-06-01 7:13 ` David Gibson
2017-06-01 7:29 ` Greg Kurz
2017-06-01 12:24 ` David Gibson
2017-06-01 15:44 ` Greg Kurz
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 4/5] pseries: Reset CPU compatibility mode David Gibson
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 5/5] ppc: Rework CPU compatibility testing across migration David Gibson
2017-06-01 6:23 ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh
2017-06-01 8:23 ` [Qemu-devel] " Greg Kurz
2017-06-02 2:25 ` David Gibson
2017-05-29 23:14 ` [Qemu-devel] [PATCHv4 0/5] Clean up compatibility mode handling Greg Kurz
2017-05-30 6:18 ` David Gibson
2017-05-30 8:01 ` Greg Kurz
2017-05-31 2:57 ` David Gibson
2017-05-31 8:58 ` Greg Kurz
2017-06-01 6:52 ` David Gibson
2017-06-01 11:59 ` Cédric Le Goater
2017-06-01 13:09 ` Greg Kurz
2017-06-02 2:00 ` David Gibson
2017-06-02 8:15 ` Greg Kurz
2017-06-04 11:09 ` David Gibson
2017-06-02 1:55 ` David Gibson [this message]
2017-06-01 6:59 ` no-reply
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=20170602015509.GG13397@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=abologna@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=clg@kaod.org \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=quintela@redhat.com \
--cc=sbobroff@redhat.com \
--cc=sursingh@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 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).