Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754918AbbBTTzR (ORCPT ); Fri, 20 Feb 2015 14:55:17 -0500 Received: from cantor2.suse.de ([195.135.220.15]:59829 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752301AbbBTTzP (ORCPT ); Fri, 20 Feb 2015 14:55:15 -0500 Message-ID: <54E7911F.3030901@suse.de> Date: Fri, 20 Feb 2015 20:55:11 +0100 From: Alexander Graf User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Michael Mueller CC: "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" , "linux-s390@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Gleb Natapov , Christian Borntraeger , "Jason J. Herne" , Cornelia Huck , Paolo Bonzini , Andreas Faerber , Richard Henderson Subject: Re: [Qemu-devel] [RFC PATCH v2 04/15] cpu-model/s390: Introduce S390 CPU models References: <1424183053-4310-1-git-send-email-mimu@linux.vnet.ibm.com> <1424183053-4310-5-git-send-email-mimu@linux.vnet.ibm.com> <54E73C8F.7000202@suse.de> <20150220160046.4743acc8@bee> <89E3550E-9E2B-4D95-A809-B7C64EBCD7C5@suse.de> <20150220164944.4eb4eeb3@bee> <54E76790.1030700@suse.de> <20150220183748.45b32e11@bee> <2049D8E0-FE03-4E84-94D0-E23B695BC865@suse.de> <20150220204303.4f20f54e@bee> In-Reply-To: <20150220204303.4f20f54e@bee> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1923 Lines: 56 On 20.02.15 20:43, Michael Mueller wrote: > On Fri, 20 Feb 2015 18:50:20 +0100 > Alexander Graf wrote: > >> >> >> >>> Am 20.02.2015 um 18:37 schrieb Michael Mueller : >>> >>> On Fri, 20 Feb 2015 17:57:52 +0100 >>> Alexander Graf wrote: >>> >>>> Because all CPUs we have in our list only expose 128 bits? >>> >>> Here a STFLE result on a EC12 GA2, already more than 128 bits... Is that model on the list? >> >> If that model has 3 elements, yes, the array should span 3. >> >> I hope it's in the list. Every model wecare about should be, no? >> > > On my list? Yes! > >>> >>> [mimu@p57lp59 s390xfac]$ ./s390xfac -b >>> fac[0] = 0xfbfffffbfcfff840 >>> fac[1] = 0xffde000000000000 >>> fac[2] = 0x1800000000000000 >>>> >>>>> I want to have this independent from a future machine of the z/Arch. The kernel stores the >>>>> full facility set, KVM does and there is no good reason for QEMU not to do. If other >>>>> accelerators decide to just implement 64 or 128 bits of facilities that's ok... >>>> >>>> So you want to support CPUs that are not part of the list? >>> >>> The architecture at least defines more than 2 or 3. Do you want me to limit it to an arbitrary >>> size?. Only in QEMU or also in the KVM interface? >> >> Only internally in QEMU. The kvm interface should definitely be as big as the spec allows! > > Right, now we're on the same page again. That can be taken in consideration. ... Although it's > just and optimization. :-) Yeah. You could also consider using the QEMU built-in bitmap type and functions and just convert from there. That would give you native support for bit values > 64. Alex -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/