From: Alex Williamson <alex.williamson@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC PATCH qemu 0/4] vfio: SPAPR IOMMU v2 (memory preregistration support)
Date: Fri, 07 Aug 2015 14:20:53 -0600 [thread overview]
Message-ID: <1438978853.4023.265.camel@redhat.com> (raw)
In-Reply-To: <55C2D1AB.9020807@ozlabs.ru>
On Thu, 2015-08-06 at 13:16 +1000, Alexey Kardashevskiy wrote:
> On 07/29/2015 10:27 AM, Alexey Kardashevskiy wrote:
> > Oh, just noticed, this is missing "v4" in the subject line.
>
> Anyone, ping? Thanks
I think David had some ideas on re-working this, but I'm not sure if
he's had any time to implement them. Thanks,
Alex
> > On 07/20/2015 05:46 PM, Alexey Kardashevskiy wrote:
> >> Yet another try, reworked the whole patchset.
> >>
> >> Here are few patches to prepare an existing listener for handling memory
> >> preregistration for SPAPR guests running on POWER8.
> >>
> >> This used to be a part of DDW patchset but now is separated as requested.
> >>
> >>
> >> Please comment. Thanks!
> >>
> >>
> >> Changes:
> >> v4:
> >> * have 2 listeners now - "iommu" and "prereg"
> >> * removed iommu_data
> >> * many smaller changes
> >>
> >> v3:
> >> * removed incorrect "vfio: Skip PCI BARs in memory listener"
> >> * removed page size changes from quirks as they did not completely fix
> >> the crashes happening on POWER8 (only total removal helps there)
> >> * added "memory: Add reporting of supported page sizes"
> >>
> >>
> >> Alexey Kardashevskiy (4):
> >> memory: Add reporting of supported page sizes
> >> vfio: Generalize IOMMU memory listener
> >> vfio: Use different page size for different IOMMU types
> >> vfio: spapr: Add SPAPR IOMMU v2 support (DMA memory preregistering)
> >>
> >> hw/ppc/spapr_iommu.c | 8 ++
> >> hw/vfio/common.c | 217
> >> +++++++++++++++++++++++++++++++++---------
> >> include/exec/memory.h | 11 +++
> >> include/hw/vfio/vfio-common.h | 26 ++---
> >> memory.c | 9 ++
> >> trace-events | 2 +
> >> 6 files changed, 214 insertions(+), 59 deletions(-)
> >>
> >
> >
>
>
prev parent reply other threads:[~2015-08-07 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 7:46 [Qemu-devel] [RFC PATCH qemu 0/4] vfio: SPAPR IOMMU v2 (memory preregistration support) Alexey Kardashevskiy
2015-07-20 7:46 ` [Qemu-devel] [RFC PATCH qemu 1/4] memory: Add reporting of supported page sizes Alexey Kardashevskiy
2015-07-20 7:46 ` [Qemu-devel] [RFC PATCH qemu 2/4] vfio: Generalize IOMMU memory listener Alexey Kardashevskiy
2015-07-20 7:46 ` [Qemu-devel] [RFC PATCH qemu 3/4] vfio: Use different page size for different IOMMU types Alexey Kardashevskiy
2015-07-20 7:46 ` [Qemu-devel] [RFC PATCH qemu 4/4] vfio: spapr: Add SPAPR IOMMU v2 support (DMA memory preregistering) Alexey Kardashevskiy
2015-07-29 0:27 ` [Qemu-devel] [RFC PATCH qemu 0/4] vfio: SPAPR IOMMU v2 (memory preregistration support) Alexey Kardashevskiy
2015-08-06 3:16 ` Alexey Kardashevskiy
2015-08-07 20:20 ` Alex Williamson [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=1438978853.4023.265.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).