From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46840) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZenqY-00076d-Gp for qemu-devel@nongnu.org; Wed, 23 Sep 2015 13:28:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZenqX-0002p7-6j for qemu-devel@nongnu.org; Wed, 23 Sep 2015 13:28:46 -0400 Message-ID: <1443029323.23936.484.camel@redhat.com> From: Alex Williamson Date: Wed, 23 Sep 2015 11:28:43 -0600 In-Reply-To: <1442647117-2726-10-git-send-email-david@gibson.dropbear.id.au> References: <1442647117-2726-1-git-send-email-david@gibson.dropbear.id.au> <1442647117-2726-10-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] [RFC PATCH 09/14] vfio: Expose a VFIO PCI device's group for EEH List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Gibson Cc: lvivier@redhat.com, thuth@redhat.com, mdroth@linux.vnet.ibm.com, aik@ozlabs.ru, qemu-devel@nongnu.org, gwshan@linux.vnet.ibm.com, qemu-ppc@nongnu.org On Sat, 2015-09-19 at 17:18 +1000, David Gibson wrote: > The Enhanced Error Handling (EEH) interface in PAPR operates on units of a > Partitionable Endpoint (PE). For VFIO devices, the PE boundaries the guest > sees must match the PE (i.e. IOMMU group) boundaries on the host. To > implement this VFIO needs to expose to EEH the IOMMU group each VFIO device > belongs to. > > Add a vfio_pci_device_group() function to the VFIO/EEH interface for this > purpose. > > Signed-off-by: David Gibson > --- > hw/vfio/pci.c | 13 +++++++++++++ > include/hw/vfio/vfio-eeh.h | 1 + > 2 files changed, 14 insertions(+) > > diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c > index 73d34b9..29f9467 100644 > --- a/hw/vfio/pci.c > +++ b/hw/vfio/pci.c > @@ -41,6 +41,7 @@ > #include "trace.h" > #include "hw/vfio/vfio.h" > #include "hw/vfio/vfio-common.h" > +#include "hw/vfio/vfio-eeh.h" Why? EEH may be the consumer, but it's not EEH specific, it should not have the prototype in an EEH specific header. > > struct VFIOPCIDevice; > > @@ -3351,6 +3352,18 @@ static void vfio_unregister_req_notifier(VFIOPCIDevice *vdev) > vdev->req_enabled = false; > } > > +VFIOGroup *vfio_pci_device_group(PCIDevice *pdev) > +{ > + VFIOPCIDevice *vdev; > + > + if (!object_dynamic_cast(OBJECT(pdev), "vfio-pci")) { > + return NULL; > + } > + > + vdev = DO_UPCAST(VFIOPCIDevice, pdev, pdev); > + return vdev->vbasedev.group; > +} > + > /* > * AMD Radeon PCI config reset, based on Linux: > * drivers/gpu/drm/radeon/ci_smc.c:ci_is_smc_running() > diff --git a/include/hw/vfio/vfio-eeh.h b/include/hw/vfio/vfio-eeh.h > index d7356f2..0ea87e1 100644 > --- a/include/hw/vfio/vfio-eeh.h > +++ b/include/hw/vfio/vfio-eeh.h > @@ -38,5 +38,6 @@ > typedef struct VFIOGroup VFIOGroup; > > int vfio_eeh_op(VFIOGroup *group, uint32_t op); > +VFIOGroup *vfio_pci_device_group(PCIDevice *pdev); > > #endif /* VFIO_EEH_H */