From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41444) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zi4ox-0005rt-2X for qemu-devel@nongnu.org; Fri, 02 Oct 2015 14:12:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zi4ot-0007LF-Te for qemu-devel@nongnu.org; Fri, 02 Oct 2015 14:12:39 -0400 Message-ID: <1443809551.26107.114.camel@redhat.com> From: Alex Williamson Date: Fri, 02 Oct 2015 12:12:31 -0600 In-Reply-To: <1443579237-9636-1-git-send-email-david@gibson.dropbear.id.au> References: <1443579237-9636-1-git-send-email-david@gibson.dropbear.id.au> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCHv3 0/7] VFIO extensions to allow VFIO devices on spapr-pci-host-bridge List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Gibson Cc: lvivier@redhat.com, thuth@redhat.com, qemu-devel@nongnu.org, aik@ozlabs.ru, abologna@redhat.com, mdroth@linux.vnet.ibm.com, qemu-ppc@nongnu.org, pbonzini@redhat.com, gwshan@linux.vnet.ibm.com On Wed, 2015-09-30 at 12:13 +1000, David Gibson wrote: > Hi Alex, > > Here are the parts of my recent series to allow VFIO devices on the > spapr-pci-host-bridge device which affect the core VFIO code. They've > been revised according to the comments from yourself and others. > > There's also one patch for the memory subsystem. > > Note that while these are motivated by the needs of the sPAPR code, > they changes should all be generally correct, and will allow safer and > more flexible use of VFIO devices in other potential situations as > well. > > Please apply. > > Changes since v2: > * Reworked IOMMU notifier replay mechanism according to Paolo's > suggestions. > Changes since v1: > * Assorted minor cleanups based on comments. > > > *** BLURB HERE *** > > David Gibson (7): > vfio: Remove unneeded union from VFIOContainer > vfio: Generalize vfio_listener_region_add failure path > vfio: Check guest IOVA ranges against host IOMMU capabilities > vfio: Record host IOMMU's available IO page sizes > memory: Allow replay of IOMMU mapping notifications AFAICT, we just need an ack of the memory API addition and then this series should be ready to go through my tree. Paolo, can you ack 5/7? Thanks, Alex > vfio: Allow hotplug of containers onto existing guest IOMMU mappings > vfio: Expose a VFIO PCI device's group for EEH > > hw/vfio/common.c | 140 ++++++++++++++++++++++++++---------------- > hw/vfio/pci.c | 14 +++++ > include/exec/memory.h | 13 ++++ > include/hw/vfio/vfio-common.h | 23 +++---- > include/hw/vfio/vfio-pci.h | 11 ++++ > memory.c | 20 ++++++ > 6 files changed, 154 insertions(+), 67 deletions(-) > create mode 100644 include/hw/vfio/vfio-pci.h >