Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4061263yba; Tue, 9 Apr 2019 10:16:59 -0700 (PDT) X-Google-Smtp-Source: APXvYqw1UC1/a83FonrNydbcaPlWjZ/RIZodhmqsKsKD8iifbhZ3pZ1RrsBjIXtGsP+/p5R5Wx0j X-Received: by 2002:a63:8142:: with SMTP id t63mr34034300pgd.63.1554830219620; Tue, 09 Apr 2019 10:16:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554830219; cv=none; d=google.com; s=arc-20160816; b=AWrB5rT2b9zqr4e6Oodpi6eNA5eSmh/INBNrc8EknxiO7J3+rZk5nd/nrUYM3YBbRY 61F4uCWh5QyKYrSG4yiSt+uZQi8RPrssZimBqmmgiUCJGv/dH3KolcWeJcSJJgcyFzVy NUYSRffCt2T2tyXJD5Dz8ZOps1nJz4tZbK+cl79+VWyKNYtVnEW4d1l9uqJDSDrTchvu nzdm2t/QHZc5NYnCuV4xVhAMpIZY22y4y+7XD7EDXycr0I2y+/Pb4vL5hdmq5TsrTV1a FrC0eeC4BxejR2PiFkElm/Eg2n9d+iiBSO2QOaPKR3xhlg8I1hIYuz99rumbrx9DxDf2 sNFQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=BlmSFcgz61xK6btqDhTNxKOXCBHYSve3PDZqMbWVjXA=; b=jvt9rGQy5CPKB4Gb2phhdkB3uBzprhKlusqexlUK9YwP7FQKKw6eECIz0M/aUS3ll9 VHUxbYhqRZpoubbUrVSjefvTl/X4JZk0O9npgVM0e2+CBuFV1oHQNGnrFA8QX/DOaITF i+vnr70EBp+MrJUAeKtnHbwQKWiul5ybDlaVpT+ymRSd9lTAwciIcr6mKwJPY1tiUgj5 MyFAzAR61tVJvaVusHoFaV7eLJug31PQQq83RA8FxQC80MtkVfg8B+j/5ActV26th9xf n5rCnGScVy0OL1zyEAmKP0N87lhnVJ1q8jy0ACpvK4kdd2XFAMWz6DMysMHN0VGtdHhN SL+g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z5si24269667pge.81.2019.04.09.10.16.43; Tue, 09 Apr 2019 10:16:59 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726680AbfDIRPZ (ORCPT + 99 others); Tue, 9 Apr 2019 13:15:25 -0400 Received: from verein.lst.de ([213.95.11.211]:51766 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726493AbfDIRPY (ORCPT ); Tue, 9 Apr 2019 13:15:24 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id D056B68B02; Tue, 9 Apr 2019 19:15:11 +0200 (CEST) Date: Tue, 9 Apr 2019 19:15:11 +0200 From: Christoph Hellwig To: Robin Murphy Cc: Christoph Hellwig , Joerg Roedel , Catalin Marinas , Will Deacon , Tom Lendacky , iommu@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 07/21] dma-iommu: move the arm64 wrappers to common code Message-ID: <20190409171511.GC14679@lst.de> References: <20190327080448.5500-1-hch@lst.de> <20190327080448.5500-8-hch@lst.de> <67573dd3-72c7-692d-bc1a-7edb49ff9551@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <67573dd3-72c7-692d-bc1a-7edb49ff9551@arm.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 09, 2019 at 04:07:02PM +0100, Robin Murphy wrote: >> +static void iommu_dma_unmap_page(struct device *dev, dma_addr_t dma_handle, >> + size_t size, enum dma_data_direction dir, unsigned long attrs) >> +{ >> + if (!(attrs & DMA_ATTR_SKIP_CPU_SYNC)) >> + iommu_dma_sync_single_for_cpu(dev, dma_handle, size, dir); >> + __iommu_dma_unmap(iommu_get_domain_for_dev(dev), dma_handle, size); > > That wants to be iommu_get_dma_domain() there to minimise the overhead. In > fact, I guess this could now be streamlined a bit in the style of > iommu_dma_map_page() above - i.e. avoid doing a second domain lookup in the > sync case - but that can happen later (if indeed you haven't already). Yes, this should be iommu_get_dma_domain - this got lost during a rebase to the kernel version that changed to the iommu_get_dma_domain calls. I don't think I've optimized to remove the additional call, but I can easily throw in another patch to do that.