From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35080) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dwRs2-0006nc-Qt for qemu-devel@nongnu.org; Mon, 25 Sep 2017 07:48:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dwRrz-00026L-I4 for qemu-devel@nongnu.org; Mon, 25 Sep 2017 07:48:18 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:39456) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dwRrs-000215-UG for qemu-devel@nongnu.org; Mon, 25 Sep 2017 07:48:15 -0400 Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v8PBhfnV047325 for ; Mon, 25 Sep 2017 07:48:00 -0400 Received: from e06smtp11.uk.ibm.com (e06smtp11.uk.ibm.com [195.75.94.107]) by mx0a-001b2d01.pphosted.com with ESMTP id 2d6wbpq28g-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Mon, 25 Sep 2017 07:48:00 -0400 Received: from localhost by e06smtp11.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 25 Sep 2017 12:47:56 +0100 References: <20170922083855.102341-1-borntraeger@de.ibm.com> <20170922083855.102341-3-borntraeger@de.ibm.com> <5e7ba7d5-82d4-f1e6-532a-37c2c445c227@linux.vnet.ibm.com> <4a31c53b-98aa-747a-1402-1a93e74c565b@de.ibm.com> <5cdfe359-2e78-7e2a-72c2-d3e69574288e@linux.vnet.ibm.com> <20170925120745.7326637e.cohuck@redhat.com> <20da1950-3aa5-c29f-3d54-4f82289f34f1@de.ibm.com> <20170925134532.08e9e273.cohuck@redhat.com> From: Christian Borntraeger Date: Mon, 25 Sep 2017 13:47:52 +0200 MIME-Version: 1.0 In-Reply-To: <20170925134532.08e9e273.cohuck@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Message-Id: <4cbc3c5b-3050-2e4e-f4cd-0c92fdb8e11f@de.ibm.com> Subject: Re: [Qemu-devel] [PATCH/RFC 2/3] s390x/ais: enable ais when migration is available List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cornelia Huck Cc: Halil Pasic , Pierre Morel , Yi Min Zhao , David Hildenbrand , qemu-devel , Alexander Graf , "Jason J . Herne" , Richard Henderson , Boris Fiuczynski On 09/25/2017 01:45 PM, Cornelia Huck wrote: > On Mon, 25 Sep 2017 12:12:49 +0200 > Christian Borntraeger wrote: > >> On 09/25/2017 12:07 PM, Cornelia Huck wrote: >>> On Fri, 22 Sep 2017 16:27:00 +0200 >>> Halil Pasic wrote: >>> >>>> One thing I would find very helpful is what do we expect to work and not >>>> work for which version. Kind of a matrix. For instance should vfio pci >>>> work for versions prior 2.11. I think in the not so distant past we >>>> changed how SIC works (so it complains when we don't have ais). >>> >>> A matrix sounds like a good idea. >> >> I think we do not even need a matrix, a minimum level will suffice because... >>> >>> I don't think we really ever had a setup that worked out of the box >> >> exactly: ...it never worked until 2.10 and we do not have libvirt support yet. >> Now with the fix 2.10 will also not work, so I think its fair to say >> >> PCI passthrough via VFIO will be supported for >> - KVM: host kernel >= 4.13 >> - TCG: TBD >> - QEMU >= 2.11 >> - libvirt TBD > > Make that zpci-per-se, no? > > with KVM: host kernel >= 4.13 && QEMU >= 2.11 > with TCG: tbd, I don't think anybody has time to wire this up for 2.11 > > Apropos libvirt: How will it determine whether zpci should be > supported? There are some old QEMU + KVM combinations out there that > will have a phb (but not be usable by stock Linux guests as the feature > bits are missing). Version fence? Check for cpu feature support? I think for multibus or something like that Boris wanted to check for a version anyway. So maybe 2.11 (now that 2.10 is broken regarding ais) as a minimum QEMU level would make sense.