From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: kvm@vger.kernel.org, Alexey Kardashevskiy <aik@ozlabs.ru>,
Alexander Graf <agraf@suse.de>,
kvm-ppc@vger.kernel.org,
Alex Williamson <alex.williamson@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Joerg Roedel <joerg.roedel@amd.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/6] KVM: PPC: IOMMU in-kernel handling
Date: Mon, 6 May 2013 17:25:51 +1000 [thread overview]
Message-ID: <1367825157-27231-1-git-send-email-aik@ozlabs.ru> (raw)
This series is supposed to accelerate IOMMU operations in real and virtual
mode in the host kernel for the KVM guest.
The first user is VFIO however this series does not contain any VFIO related
code as the connection between VFIO and the new handlers is to be made in QEMU
via ioctl to the KVM fd.
Although the series compiles, it does not make sense without VFIO patches which
are posted separately.
The "iommu: Add a function to find an iommu group by id" patch has already
gone to linux-next (from iommu tree) but it is not in upstream yet so
I am including it here for the reference.
Alexey Kardashevskiy (6):
KVM: PPC: Make lookup_linux_pte public
KVM: PPC: Add support for multiple-TCE hcalls
powerpc: Prepare to support kernel handling of IOMMU map/unmap
iommu: Add a function to find an iommu group by id
KVM: PPC: Add support for IOMMU in-kernel handling
KVM: PPC: Add hugepage support for IOMMU in-kernel handling
Documentation/virtual/kvm/api.txt | 43 +++
arch/powerpc/include/asm/kvm_host.h | 4 +
arch/powerpc/include/asm/kvm_ppc.h | 44 ++-
arch/powerpc/include/asm/pgtable-ppc64.h | 4 +
arch/powerpc/include/uapi/asm/kvm.h | 7 +
arch/powerpc/kvm/book3s_64_vio.c | 433 +++++++++++++++++++++++++++-
arch/powerpc/kvm/book3s_64_vio_hv.c | 464 ++++++++++++++++++++++++++++--
arch/powerpc/kvm/book3s_hv.c | 23 ++
arch/powerpc/kvm/book3s_hv_rm_mmu.c | 5 +-
arch/powerpc/kvm/book3s_hv_rmhandlers.S | 6 +
arch/powerpc/kvm/book3s_pr_papr.c | 37 ++-
arch/powerpc/kvm/powerpc.c | 15 +
arch/powerpc/mm/init_64.c | 77 ++++-
drivers/iommu/iommu.c | 29 ++
include/linux/iommu.h | 1 +
include/uapi/linux/kvm.h | 3 +
16 files changed, 1159 insertions(+), 36 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-05-06 7:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 7:25 Alexey Kardashevskiy [this message]
2013-05-06 7:25 ` [PATCH 1/6] KVM: PPC: Make lookup_linux_pte public Alexey Kardashevskiy
2013-05-06 7:25 ` [PATCH 2/6] KVM: PPC: Add support for multiple-TCE hcalls Alexey Kardashevskiy
2013-05-07 5:05 ` David Gibson
2013-05-10 6:51 ` David Gibson
2013-05-10 7:53 ` Alexey Kardashevskiy
2013-05-06 7:25 ` [PATCH 3/6] powerpc: Prepare to support kernel handling of IOMMU map/unmap Alexey Kardashevskiy
2013-05-06 7:25 ` [PATCH 4/6] iommu: Add a function to find an iommu group by id Alexey Kardashevskiy
2013-05-06 7:25 ` [PATCH 5/6] KVM: PPC: Add support for IOMMU in-kernel handling Alexey Kardashevskiy
2013-05-07 5:29 ` David Gibson
2013-05-07 5:51 ` Alexey Kardashevskiy
2013-05-07 6:02 ` David Gibson
2013-05-07 6:27 ` Alexey Kardashevskiy
2013-05-07 6:54 ` David Gibson
2013-05-06 7:25 ` [PATCH 6/6] KVM: PPC: Add hugepage " Alexey Kardashevskiy
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=1367825157-27231-1-git-send-email-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=joerg.roedel@amd.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@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).