From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUwr5-0001Cb-63 for qemu-devel@nongnu.org; Fri, 19 Sep 2014 08:00:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XUwqs-0008Uv-QS for qemu-devel@nongnu.org; Fri, 19 Sep 2014 08:00:03 -0400 Received: from e06smtp14.uk.ibm.com ([195.75.94.110]:60719) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUwqs-0008U6-Gj for qemu-devel@nongnu.org; Fri, 19 Sep 2014 07:59:50 -0400 Received: from /spool/local by e06smtp14.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 19 Sep 2014 12:59:43 +0100 Received: from b06cxnps4074.portsmouth.uk.ibm.com (d06relay11.portsmouth.uk.ibm.com [9.149.109.196]) by d06dlp03.portsmouth.uk.ibm.com (Postfix) with ESMTP id 1A32D1B08049 for ; Fri, 19 Sep 2014 13:00:48 +0100 (BST) Received: from d06av07.portsmouth.uk.ibm.com (d06av07.portsmouth.uk.ibm.com [9.149.37.248]) by b06cxnps4074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id s8JBxeld34668762 for ; Fri, 19 Sep 2014 11:59:40 GMT Received: from d06av07.portsmouth.uk.ibm.com (localhost [127.0.0.1]) by d06av07.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s8JBxeQY017992 for ; Fri, 19 Sep 2014 07:59:40 -0400 Message-Id: <20140919115429.557279920@de.ibm.com> Date: Fri, 19 Sep 2014 13:54:29 +0200 From: frank.blaschka@de.ibm.com Subject: [Qemu-devel] [RFC patch 0/6] vfio based pci pass-through for qemu/KVM on s390 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, linux-s390@vger.kernel.org, kvm@vger.kernel.org Cc: pbonzini@redhat.com, alex.williamson@redhat.com, agraf@suse.de This set of patches implements a vfio based solution for pci pass-through on the s390 platform. The kernel stuff is pretty much straight forward, but qemu needs more work. Most interesting patch is: vfio: make vfio run on s390 platform I hope Alex & Alex can give me some guidance how to do the changes in an appropriate way. After creating a separate iommmu address space for each attached PCI device I can successfully run the vfio type1 iommu. So If we could extend type1 not registering all guest memory (see patch) I think we do not need a special vfio iommu for s390 for the moment. The patches implement the base pass-through support. s390 specific virtualization functions are currently not included. This would be a second step after the base support is done. kernel patches apply to linux-kvm-next KVM: s390: Enable PCI instructions iommu: add iommu for s390 platform vfio: make vfio build on s390 qemu patches apply to qemu-master s390: Add PCI bus support s390: implement pci instruction vfio: make vfio run on s390 platform Thx for feedback and review comments Frank