From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
alex.williamson@redhat.com, pbonzini@redhat.com
Cc: thuth@redhat.com, qemu-ppc@nongnu.org, abologna@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv2 0/7] VFIO extensions to allow VFIO devices on spapr-pci-host-bridge
Date: Fri, 25 Sep 2015 17:27:13 +0200 [thread overview]
Message-ID: <560567D1.9040007@redhat.com> (raw)
In-Reply-To: <1443180908-19911-1-git-send-email-david@gibson.dropbear.id.au>
On 25/09/2015 13:35, 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. Paolo can you let me
> know if this needs to be sent separately.
>
> 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 v1:
> * Assorted minor cleanups based on comments.
>
> 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
> 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 | 17 +++++
> include/hw/vfio/vfio-common.h | 23 +++----
> include/hw/vfio/vfio-pci.h | 11 ++++
> memory.c | 23 +++++++
> 6 files changed, 160 insertions(+), 68 deletions(-)
> create mode 100644 include/hw/vfio/vfio-pci.h
>
For the series:
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
prev parent reply other threads:[~2015-09-25 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 11:35 [Qemu-devel] [PATCHv2 0/7] VFIO extensions to allow VFIO devices on spapr-pci-host-bridge David Gibson
2015-09-25 11:35 ` [Qemu-devel] [PATCHv2 1/7] vfio: Remove unneeded union from VFIOContainer David Gibson
2015-09-25 11:35 ` [Qemu-devel] [PATCHv2 2/7] vfio: Generalize vfio_listener_region_add failure path David Gibson
2015-09-25 11:35 ` [Qemu-devel] [PATCHv2 3/7] vfio: Check guest IOVA ranges against host IOMMU capabilities David Gibson
2015-09-25 11:35 ` [Qemu-devel] [PATCHv2 4/7] vfio: Record host IOMMU's available IO page sizes David Gibson
2015-09-25 11:35 ` [Qemu-devel] [PATCHv2 5/7] memory: Allow replay of IOMMU mapping notifications David Gibson
2015-09-25 11:35 ` [Qemu-devel] [PATCHv2 6/7] vfio: Allow hotplug of containers onto existing guest IOMMU mappings David Gibson
2015-09-25 11:35 ` [Qemu-devel] [PATCHv2 7/7] vfio: Expose a VFIO PCI device's group for EEH David Gibson
2015-09-25 15:27 ` Laurent Vivier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=560567D1.9040007@redhat.com \
--to=lvivier@redhat.com \
--cc=abologna@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.