From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56060) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1beNq9-00036O-MK for qemu-devel@nongnu.org; Mon, 29 Aug 2016 10:47:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1beNq4-0001ek-Nc for qemu-devel@nongnu.org; Mon, 29 Aug 2016 10:47:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42148) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1beNq4-0001e7-Fi for qemu-devel@nongnu.org; Mon, 29 Aug 2016 10:47:04 -0400 References: <1472062266-53206-2-git-send-email-dahi@linux.vnet.ibm.com> <20160829101358.14564-1-dahi@linux.vnet.ibm.com> From: Eric Blake Message-ID: <57C44AE5.1070505@redhat.com> Date: Mon, 29 Aug 2016 09:47:01 -0500 MIME-Version: 1.0 In-Reply-To: <20160829101358.14564-1-dahi@linux.vnet.ibm.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="uG0UVqFXVCSvC8S0kWe3nMqWQN59lxBt3" Subject: Re: [Qemu-devel] [Patch 01/30] qmp: details about CPU definitions in query-cpu-definitions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Hildenbrand , qemu-devel@nongnu.org Cc: ehabkost@redhat.com, borntraeger@de.ibm.com, fiuczy@linux.vnet.ibm.com, cornelia.huck@de.ibm.com, imammedo@redhat.com, jdenemar@redhat.com, mimu@linux.vnet.ibm.com This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --uG0UVqFXVCSvC8S0kWe3nMqWQN59lxBt3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 08/29/2016 05:13 AM, David Hildenbrand wrote: > It might be of interest for tooling whether a CPU definition can be saf= ely > used when migrating, or if e.g. CPU features might get lost during > migration when migrationg from/to a different QEMU version or host, eve= n if > the same compatibility machine is used. >=20 > Also, we want to know if a CPU definition is static and will never chan= ge. > Beause these definitions can then be used independantly of a compatibil= ity > machine and will always have the same feature set, they can e.g. be use= d > to indicate the "host" model in libvirt later on. >=20 > Let's add two return values to query-cpu-definitions, stating for each > returned CPU definition, if it is migration-safe and if it is static. >=20 > While "migration-safe" is optional, "static" will be set to "false" > automatically by all implementing architectures. If a model really was > static all the time and will be in the future, this can simply be chang= ed > later. >=20 > Signed-off-by: David Hildenbrand > --- > qapi-schema.json | 14 +++++++++++++- > 1 file changed, 13 insertions(+), 1 deletion(-) Reviewed-by: Eric Blake --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --uG0UVqFXVCSvC8S0kWe3nMqWQN59lxBt3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJXxErlAAoJEKeha0olJ0Nq4JoH/iv8u4LxVIc8PnknuzcjMlYa 071WmVHTEbMbIjd7pqDSVEweZKvH1rrGp+olP5LwDUNfvfxEvO0UQ1o/pKUSkP8W iRbxNc86KziV+MM6oVMBOwSY4hsrgCLeDcFNEWOUo8oUNHDJVVonnmgcTmh9kyfc 6wtpvfXJ3UpHdqTvXshW4OlEwEGhtB/4+CXZWSnCnT6N5oJ/mkWd2bpGD+U1Eu57 dpmd8SXFt1MzisgbdW+HHCH5VwupERp2xs6lwTYRhpbSLZMmgA8upjbPoSy+2ib+ G5ChNEhUsHxK6mnhZfCv8iMZRxudQNgISDCrnjrXEnSsH9K2Pl2rJwZUtejE6f0= =2tmP -----END PGP SIGNATURE----- --uG0UVqFXVCSvC8S0kWe3nMqWQN59lxBt3--