From: Andrea Bolognani <abologna@redhat.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: sbobroff@redhat.com, qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv5 0/4] Clean up compatibility mode handling
Date: Sat, 10 Jun 2017 17:42:45 +0200 [thread overview]
Message-ID: <1497109365.4161.1.camel@redhat.com> (raw)
In-Reply-To: <20170602031507.29881-1-david@gibson.dropbear.id.au>
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.
I've tested this the same way I had tested one of the
previous respins, eg. for basic usage and general sanity
of the interface. All the issues I pointed out last time
seems to have been addressed.
Tested-by: Andrea Bolognani <abologna@redhat.com>
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2017-06-10 15:42 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 [this message]
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=1497109365.4161.1.camel@redhat.com \
--to=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).