From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51142) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7nL3-0003pl-0Y for qemu-devel@nongnu.org; Wed, 24 Jun 2015 12:15:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z7nKy-0007LP-Ku for qemu-devel@nongnu.org; Wed, 24 Jun 2015 12:15:48 -0400 Received: from cantor2.suse.de ([195.135.220.15]:44038 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7nKy-0007Kj-Eq for qemu-devel@nongnu.org; Wed, 24 Jun 2015 12:15:44 -0400 Message-ID: <558AD7AF.4080804@suse.de> Date: Wed, 24 Jun 2015 18:15:43 +0200 From: =?windows-1252?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <20150623162555.GL30318@redhat.com> <20150623183115-mutt-send-email-mst@redhat.com> <20150623164204.GM30318@redhat.com> <55898D94.4070702@suse.de> <20150623171122.GI3134@thinpad.lan.raisama.net> <20150623213445.GA17756@redhat.com> <20150624142446.GU3134@thinpad.lan.raisama.net> <20150624162659-mutt-send-email-mst@redhat.com> <20150624154429.GW3134@thinpad.lan.raisama.net> <558AD39A.1070607@suse.de> <20150624160852.GY3134@thinpad.lan.raisama.net> In-Reply-To: <20150624160852.GY3134@thinpad.lan.raisama.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Not introducing new host-side requirements on new machine-type versions (was Re: [PATCH 0/2] target-i386: "custom" CPU model + script to dump existing CPU models) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: mimu@linux.vnet.ibm.com, "Michael S. Tsirkin" , qemu-devel@nongnu.org, Alexander Graf , borntraeger@de.ibm.com, Igor Mammedov , Paolo Bonzini , Jiri Denemark , rth@twiddle.net Am 24.06.2015 um 18:08 schrieb Eduardo Habkost: > On Wed, Jun 24, 2015 at 05:58:18PM +0200, Andreas F=E4rber wrote: >> Are we at the same point of stability guarantee for ppc POWER? >> For s390x, arm and aarch64 I guess not yet? >=20 > That's a good question, and I have no idea how difficult it would be to > implement that guarantee in those machines. >=20 > In s390x we are implementing machine-type-dependent "runnable" info on > query-cpu-definitions, but I don't know what the use caes look like, an= d > what are the consequences for libvirt and OpenStack. I assume this discussion is going to be summarized on the Wiki at some point. Just be sure to explicitly mention x86 then, to be safe. Cheers, Andreas --=20 SUSE Linux GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Felix Imend=F6rffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB 21284 (AG N=FCrnberg)