From: Ram Pai <linuxram@us.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: andmike@us.ibm.com, mst@redhat.com, aik@ozlabs.ru,
linuxram@us.ibm.com, mdroth@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, ram.n.pai@gmail.com, cai@lca.pw,
tglx@linutronix.de, sukadev@linux.vnet.ibm.com, hch@lst.de,
bauerman@linux.ibm.com, david@gibson.dropbear.id.au
Subject: [RFC v1 2/2] powerpc/pseries/iommu: Use dma_iommu_ops for Secure VMs aswell.
Date: Mon, 4 Nov 2019 13:28:43 -0800 [thread overview]
Message-ID: <1572902923-8096-3-git-send-email-linuxram@us.ibm.com> (raw)
In-Reply-To: <1572902923-8096-2-git-send-email-linuxram@us.ibm.com>
This enables IOMMU support for pseries Secure VMs.
Signed-off-by: Ram Pai <linuxram@us.ibm.com>
---
arch/powerpc/platforms/pseries/iommu.c | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/iommu.c b/arch/powerpc/platforms/pseries/iommu.c
index 07f0847..189717b 100644
--- a/arch/powerpc/platforms/pseries/iommu.c
+++ b/arch/powerpc/platforms/pseries/iommu.c
@@ -1333,15 +1333,7 @@ void iommu_init_early_pSeries(void)
of_reconfig_notifier_register(&iommu_reconfig_nb);
register_memory_notifier(&iommu_mem_nb);
- /*
- * Secure guest memory is inacessible to devices so regular DMA isn't
- * possible.
- *
- * In that case keep devices' dma_map_ops as NULL so that the generic
- * DMA code path will use SWIOTLB to bounce buffers for DMA.
- */
- if (!is_secure_guest())
- set_pci_dma_ops(&dma_iommu_ops);
+ set_pci_dma_ops(&dma_iommu_ops);
}
static int __init disable_multitce(char *str)
--
1.8.3.1
WARNING: multiple messages have this Message-ID (diff)
From: Ram Pai <linuxram@us.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: benh@kernel.crashing.org, david@gibson.dropbear.id.au,
mpe@ellerman.id.au, paulus@ozlabs.org, mdroth@linux.vnet.ibm.com,
hch@lst.de, linuxram@us.ibm.com, andmike@us.ibm.com,
sukadev@linux.vnet.ibm.com, mst@redhat.com, ram.n.pai@gmail.com,
aik@ozlabs.ru, cai@lca.pw, tglx@linutronix.de,
bauerman@linux.ibm.com, linux-kernel@vger.kernel.org
Subject: [RFC v1 2/2] powerpc/pseries/iommu: Use dma_iommu_ops for Secure VMs aswell.
Date: Mon, 4 Nov 2019 13:28:43 -0800 [thread overview]
Message-ID: <1572902923-8096-3-git-send-email-linuxram@us.ibm.com> (raw)
In-Reply-To: <1572902923-8096-2-git-send-email-linuxram@us.ibm.com>
This enables IOMMU support for pseries Secure VMs.
Signed-off-by: Ram Pai <linuxram@us.ibm.com>
---
arch/powerpc/platforms/pseries/iommu.c | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/iommu.c b/arch/powerpc/platforms/pseries/iommu.c
index 07f0847..189717b 100644
--- a/arch/powerpc/platforms/pseries/iommu.c
+++ b/arch/powerpc/platforms/pseries/iommu.c
@@ -1333,15 +1333,7 @@ void iommu_init_early_pSeries(void)
of_reconfig_notifier_register(&iommu_reconfig_nb);
register_memory_notifier(&iommu_mem_nb);
- /*
- * Secure guest memory is inacessible to devices so regular DMA isn't
- * possible.
- *
- * In that case keep devices' dma_map_ops as NULL so that the generic
- * DMA code path will use SWIOTLB to bounce buffers for DMA.
- */
- if (!is_secure_guest())
- set_pci_dma_ops(&dma_iommu_ops);
+ set_pci_dma_ops(&dma_iommu_ops);
}
static int __init disable_multitce(char *str)
--
1.8.3.1
next prev parent reply other threads:[~2019-11-04 21:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 21:28 [RFC v1 0/2] Enable IOMMU support for pseries Secure VMs Ram Pai
2019-11-04 21:28 ` Ram Pai
2019-11-04 21:28 ` [RFC v1 1/2] powerpc/pseries/iommu: Share the per-cpu TCE page with the hypervisor Ram Pai
2019-11-04 21:28 ` Ram Pai
2019-11-04 21:28 ` Ram Pai [this message]
2019-11-04 21:28 ` [RFC v1 2/2] powerpc/pseries/iommu: Use dma_iommu_ops for Secure VMs aswell Ram Pai
2019-11-07 10:26 ` Michael Ellerman
2019-11-07 10:26 ` Michael Ellerman
2019-11-08 5:49 ` Ram Pai
2019-11-08 5:49 ` Ram Pai
2019-11-06 1:58 ` [RFC v1 1/2] powerpc/pseries/iommu: Share the per-cpu TCE page with the hypervisor Alexey Kardashevskiy
2019-11-06 1:58 ` Alexey Kardashevskiy
2019-11-06 17:01 ` Ram Pai
2019-11-06 17:01 ` Ram Pai
2019-11-07 5:58 ` Alexey Kardashevskiy
2019-11-07 5:58 ` Alexey Kardashevskiy
2019-11-07 10:29 ` Michael Ellerman
2019-11-07 10:29 ` Michael Ellerman
2019-11-08 6:05 ` Ram Pai
2019-11-08 6:05 ` Ram Pai
2019-11-06 1:59 ` [RFC v1 0/2] Enable IOMMU support for pseries Secure VMs Alexey Kardashevskiy
2019-11-06 1:59 ` Alexey Kardashevskiy
2019-11-06 16:46 ` Ram Pai
2019-11-06 16:46 ` Ram Pai
2019-11-06 18:06 ` Michael S. Tsirkin
2019-11-06 18:06 ` Michael S. Tsirkin
2019-11-06 18:52 ` Michael Roth
2019-11-06 18:52 ` Michael Roth
2019-11-06 22:22 ` Ram Pai
2019-11-06 22:22 ` Ram Pai
2019-11-07 6:01 ` Alexey Kardashevskiy
2019-11-07 6:01 ` 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=1572902923-8096-3-git-send-email-linuxram@us.ibm.com \
--to=linuxram@us.ibm.com \
--cc=aik@ozlabs.ru \
--cc=andmike@us.ibm.com \
--cc=bauerman@linux.ibm.com \
--cc=cai@lca.pw \
--cc=david@gibson.dropbear.id.au \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=ram.n.pai@gmail.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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.