From: David Gibson <david@gibson.dropbear.id.au>
To: Andrea Bolognani <abologna@redhat.com>
Cc: groug@kaod.org, clg@kaod.org, mdroth@linux.vnet.ibm.com,
sursingh@redhat.com, bharata@linux.vnet.ibm.com,
nikunj@linux.vnet.ibm.com, qemu-devel@nongnu.org,
qemu-ppc@nongnu.org, sbobroff@redhat.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCHv5 0/4] Clean up compatibility mode handling
Date: Tue, 13 Jun 2017 16:09:45 +0800 [thread overview]
Message-ID: <20170613080945.GD30171@umbus> (raw)
In-Reply-To: <1497337300.27606.7.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On Tue, Jun 13, 2017 at 03:01:40PM +0800, Andrea Bolognani wrote:
> On Fri, 2017-06-02 at 13:15 +1000, David Gibson wrote:
> > This is a rebased and revised version of my patches revising CPU
> > compatiblity mode handling on ppc, last posted in November. Since
> > then, many of the patches have already been merged (some for 2.9, some
> > since). This is what's left.
>
> As discussed yesterday on libvir-list, the current
> implementation will abort() when the user attempts to use
> a compat mode that's not valid for the host CPU, eg. on
> a POWER8 host:
>
> $ qemu-system-ppc64 \
> -nodefaults \
> -M pseries,accel=kvm \
> -cpu host,compat=power9
> Unexpected error in ppc_set_compat() at target/ppc/compat.c:135:
> qemu-system-ppc64: Compatibility PVR 0x0f000005 not valid for CPU
> Aborted
>
> We should probably report the error to the user in a slightly
> less destructive fashion :)
Good point. As I suspected, this was just an &error_abort somewhere I
should have used an &error_fatal. Fixed in the ppc-for-2.10 I just
pushed.
--
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 --]
prev parent reply other threads:[~2017-06-13 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 3:15 [Qemu-devel] [PATCHv5 0/4] Clean up compatibility mode handling David Gibson
2017-06-02 3:15 ` [Qemu-devel] [PATCHv5 1/4] qapi: add explicit null to string input and output visitors David Gibson
2017-06-02 3:15 ` [Qemu-devel] [PATCHv5 2/4] pseries: Move CPU compatibility property to machine David Gibson
2017-06-08 6:02 ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh
2017-06-09 13:55 ` [Qemu-devel] " Greg Kurz
2017-06-11 12:30 ` David Gibson
2017-06-02 3:15 ` [Qemu-devel] [PATCHv5 3/4] pseries: Reset CPU compatibility mode David Gibson
2017-06-02 3:15 ` [Qemu-devel] [PATCHv5 4/4] ppc: Rework CPU compatibility testing across migration David Gibson
2017-06-14 8:28 ` Greg Kurz
2017-06-02 3:55 ` [Qemu-devel] [PATCHv5 0/4] Clean up compatibility mode handling no-reply
2017-06-02 7:23 ` David Gibson
2017-06-08 4:17 ` David Gibson
2017-06-08 6:03 ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh
2017-06-08 8:57 ` [Qemu-devel] " Greg Kurz
2017-06-10 15:42 ` Andrea Bolognani
2017-06-11 12:57 ` David Gibson
2017-06-13 7:01 ` [Qemu-devel] [Qemu-ppc] " Andrea Bolognani
2017-06-13 8:09 ` David Gibson [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=20170613080945.GD30171@umbus \
--to=david@gibson.dropbear.id.au \
--cc=abologna@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--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=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 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.