From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 0/5 v2] VFIO PPC64: add VFIO support on POWERPC64
Date: Fri, 24 May 2013 13:14:42 +1000 [thread overview]
Message-ID: <519EDB22.1050509@ozlabs.ru> (raw)
In-Reply-To: <1369320984.2646.135.camel@ul30vt.home>
On 05/24/2013 12:56 AM, Alex Williamson wrote:
> On Tue, 2013-05-21 at 13:33 +1000, Alexey Kardashevskiy wrote:
>> The series adds support for VFIO on POWERPC in user space (such as QEMU).
>> The in-kernel real mode IOMMU support is added by another series posted
>> separately.
>>
>> As the first and main aim of this series is the POWERNV platform support,
>> the "Enable on POWERNV platform" patch goes first and introduces an API
>> to be used by the VFIO IOMMU driver. The "Enable on pSeries platform" patch
>> simply registers PHBs in the IOMMU subsystem and expects the API to be present,
>> it enables VFIO support in fully emulated QEMU guests.
>>
>> The main change is that this series was changed and tested against v3.10-rc1.
>> It also contains some bugfixes which are mentioned (if any) in the patch messages.
>>
>> Alexey Kardashevskiy (3):
>> powerpc/vfio: Enable on POWERNV platform
>> powerpc/vfio: Implement IOMMU driver for VFIO
>> powerpc/vfio: Enable on pSeries platform
>>
>> Documentation/vfio.txt | 63 +++++
>> arch/powerpc/include/asm/iommu.h | 26 ++
>> arch/powerpc/kernel/iommu.c | 323 +++++++++++++++++++++++
>> arch/powerpc/platforms/powernv/pci-ioda.c | 1 +
>> arch/powerpc/platforms/powernv/pci-p5ioc2.c | 5 +-
>> arch/powerpc/platforms/powernv/pci.c | 2 +
>> arch/powerpc/platforms/pseries/iommu.c | 4 +
>> drivers/iommu/Kconfig | 8 +
>> drivers/vfio/Kconfig | 6 +
>> drivers/vfio/Makefile | 1 +
>> drivers/vfio/vfio.c | 1 +
>> drivers/vfio/vfio_iommu_spapr_tce.c | 377 +++++++++++++++++++++++++++
>> include/uapi/linux/vfio.h | 34 +++
>> 13 files changed, 850 insertions(+), 1 deletion(-)
>> create mode 100644 drivers/vfio/vfio_iommu_spapr_tce.c
>>
>
> These look ok to me, how do you want to integrate them? Should I
> provide Acks on patches 2 & 3 and let them get pushed through the ppc
> tree or should I wait for patch 1 then push 2 & 3 through my tree?
Please ack on 2 & 3 and Ben will merge all three into his tree. Thanks!
--
Alexey
prev parent reply other threads:[~2013-05-24 3:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 3:33 [PATCH 0/5 v2] VFIO PPC64: add VFIO support on POWERPC64 Alexey Kardashevskiy
2013-05-21 3:33 ` [PATCH 1/3] powerpc/vfio: Enable on POWERNV platform Alexey Kardashevskiy
2013-12-12 23:35 ` [1/3] " Scott Wood
2013-12-13 3:02 ` Alexey Kardashevskiy
2013-12-13 21:02 ` Scott Wood
2013-12-14 4:56 ` Bharat.Bhushan
2013-05-21 3:33 ` [PATCH 2/3] powerpc/vfio: Implement IOMMU driver for VFIO Alexey Kardashevskiy
2013-05-24 14:03 ` Alex Williamson
2013-05-21 3:33 ` [PATCH 3/3] powerpc/vfio: Enable on pSeries platform Alexey Kardashevskiy
2013-05-24 14:03 ` Alex Williamson
2013-05-21 3:34 ` [PATCH 0/5 v2] VFIO PPC64: add VFIO support on POWERPC64 Alexey Kardashevskiy
2013-05-23 14:56 ` Alex Williamson
2013-05-24 3:14 ` Alexey Kardashevskiy [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=519EDB22.1050509@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).