From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
To: David Gibson <david@gibson.dropbear.id.au>,
groug@kaod.org, clg@kaod.org, mdroth@linux.vnet.ibm.com,
sursingh@redhat.com, bharata@linux.vnet.ibm.com,
nikunj@linux.vnet.ibm.com
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, abologna@redhat.com,
sbobroff@redhat.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCHv5 0/4] Clean up compatibility mode handling
Date: Thu, 08 Jun 2017 16:03:51 +1000 [thread overview]
Message-ID: <1496901831.2261.4.camel@gmail.com> (raw)
In-Reply-To: <20170608041739.GY13397@umbus.fritz.box>
On Thu, 2017-06-08 at 14:17 +1000, David Gibson wrote:
> On Fri, Jun 02, 2017 at 01:15:03PM +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.
> >
> > * There was conceptual confusion about what a compatibility mode
> > means, and how it interacts with the machine type. This cleans
> > that up, clarifying that a compatibility mode (as an externally
> > set
> > option) only makes sense on machine types that don't permit the
> > guest hypervisor privilege (i.e. 'pseries')
> >
> > * It was previously the user's (or management layer's)
> > responsibility
> > to determine compatibility of CPUs on either end for migration.
> > This uses the compatibility modes to check that properly during
> > an
> > incoming migration.
>
> Anyone willing to give some review and/or testing, particularly for
> patch 2/4.
>
Sorry I had been playing around with this and meant to give it a
Tested-by
next prev parent reply other threads:[~2017-06-08 6:04 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 ` Suraj Jitindar Singh [this message]
2017-06-08 8:57 ` 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
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=1496901831.2261.4.camel@gmail.com \
--to=sjitindarsingh@gmail.com \
--cc=abologna@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--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 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).