linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>, Alexander Graf <agraf@suse.de>,
	kvm@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: [PATCH 06/10] KVM: PPC: enable IOMMU_API for KVM_BOOK3S_64 permanently
Date: Thu,  1 Aug 2013 14:44:28 +1000	[thread overview]
Message-ID: <1375332272-22176-7-git-send-email-aik@ozlabs.ru> (raw)
In-Reply-To: <1375332272-22176-1-git-send-email-aik@ozlabs.ru>

It does not make much sense to have KVM in book3s-64bit and
not to have IOMMU bits for PCI pass through support as it costs little
and allows VFIO to function on book3s-kvm.

Having IOMMU_API always enabled makes it unnecessary to have a lot of
"#ifdef IOMMU_API" in arch/powerpc/kvm/book3s_64_vio*. With those
ifdef's we could have only user space emulated devices accelerated
(but not VFIO) which do not seem to be very useful.

Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
---
 arch/powerpc/kvm/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/powerpc/kvm/Kconfig b/arch/powerpc/kvm/Kconfig
index c55c538..3b2b761 100644
--- a/arch/powerpc/kvm/Kconfig
+++ b/arch/powerpc/kvm/Kconfig
@@ -59,6 +59,7 @@ config KVM_BOOK3S_64
 	depends on PPC_BOOK3S_64
 	select KVM_BOOK3S_64_HANDLER
 	select KVM
+	select SPAPR_TCE_IOMMU
 	---help---
 	  Support running unmodified book3s_64 and book3s_32 guest kernels
 	  in virtual machines on book3s_64 host processors.
-- 
1.8.3.2


  parent reply	other threads:[~2013-08-01  4:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  4:44 [PATCH 00/10 v7] KVM: PPC: IOMMU in-kernel handling Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 01/10] hashtable: add hash_for_each_possible_rcu_notrace() Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 02/10] KVM: PPC: reserve a capability number for multitce support Alexey Kardashevskiy
2013-08-14  0:51   ` Benjamin Herrenschmidt
2013-08-26 12:37     ` Gleb Natapov
2013-08-27  4:19       ` Benjamin Herrenschmidt
2013-08-27  4:22         ` Benjamin Herrenschmidt
2013-08-27  6:41           ` Gleb Natapov
2013-08-27  7:35             ` Benjamin Herrenschmidt
2013-08-27  6:40         ` Gleb Natapov
2013-08-27  7:34           ` Benjamin Herrenschmidt
2013-08-01  4:44 ` [PATCH 03/10] KVM: PPC: reserve a capability and ioctl numbers for realmode VFIO Alexey Kardashevskiy
2013-08-15  7:16   ` Alexander Graf
2013-08-15  7:22     ` Alexey Kardashevskiy
2013-08-15  7:24       ` Alexander Graf
2013-08-15  7:25         ` Alexander Graf
2013-08-15  7:42           ` Alexey Kardashevskiy
2013-08-15  7:43             ` Alexander Graf
2013-08-15  7:54               ` Alexey Kardashevskiy
2013-08-15  7:56                 ` Alexander Graf
2013-08-01  4:44 ` [PATCH 04/10] powerpc: Prepare to support kernel handling of IOMMU map/unmap Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 05/10] powerpc: add real mode support for dma operations on powernv Alexey Kardashevskiy
2013-08-01  4:44 ` Alexey Kardashevskiy [this message]
2013-08-01  4:44 ` [PATCH 07/10] KVM: PPC: Add support for multiple-TCE hcalls Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 08/10] powerpc/iommu: rework to support realmode Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 09/10] KVM: PPC: Add support for IOMMU in-kernel handling Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 10/10] KVM: PPC: Add hugepage " Alexey Kardashevskiy
  -- strict thread matches above, loose matches on Subject: below --
2013-07-16  0:53 [PATCH 00/10 v6] KVM: PPC: " Alexey Kardashevskiy
2013-07-16  0:54 ` [PATCH 06/10] KVM: PPC: enable IOMMU_API for KVM_BOOK3S_64 permanently 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=1375332272-22176-7-git-send-email-aik@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=agraf@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@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).