From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thiago Jung Bauermann Subject: [RFC PATCH 05/11] powerpc/svm: Don't release SWIOTLB buffers on secure guests Date: Fri, 24 Aug 2018 13:25:29 -0300 Message-ID: <20180824162535.22798-6-bauerman@linux.ibm.com> References: <20180824162535.22798-1-bauerman@linux.ibm.com> Return-path: In-Reply-To: <20180824162535.22798-1-bauerman@linux.ibm.com> Sender: linux-kernel-owner@vger.kernel.org To: linuxppc-dev@lists.ozlabs.org Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Alexey Kardashevskiy , Anshuman Khandual , Benjamin Herrenschmidt , Christoph Hellwig , Michael Ellerman , Mike Anderson , Paul Mackerras , Ram Pai , Anshuman Khandual , Thiago Jung Bauermann List-Id: iommu@lists.linux-foundation.org From: Anshuman Khandual Even though SWIOTLB slab gets allocated and initialized on each powerpc platform with swiotlb_init(), it gets released away again on all server platforms because ppc_swiotlb_enable variable never gets set. Secure guests would require SWIOTLB DMA API support for virtio bounce buffering purpose. Hence retain the allocated buffer by setting ppc_swiotlb_enable variable for secure guests on Ultravisor platforms. Signed-off-by: Anshuman Khandual Signed-off-by: Thiago Jung Bauermann --- arch/powerpc/kernel/svm.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/powerpc/kernel/svm.c b/arch/powerpc/kernel/svm.c index eab2a64d8643..891db2de8c04 100644 --- a/arch/powerpc/kernel/svm.c +++ b/arch/powerpc/kernel/svm.c @@ -16,6 +16,7 @@ static int __init init_svm(void) if (!is_svm_platform()) return 0; + ppc_swiotlb_enable = 1; swiotlb_update_mem_attributes(); return 0;