From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from foss.arm.com (usa-sjc-mx-foss1.foss.arm.com [217.140.101.70]) by lists.ozlabs.org (Postfix) with ESMTP id 42Lf976xYnzDrJD for ; Fri, 28 Sep 2018 01:38:35 +1000 (AEST) Subject: Re: [PATCH 3/5] dma-direct: refine dma_direct_alloc zone selection To: Christoph Hellwig Cc: iommu@lists.linux-foundation.org, Marek Szyprowski , Benjamin Herrenschmidt , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org References: <20180920185247.20037-1-hch@lst.de> <20180920185247.20037-4-hch@lst.de> <20180927153028.GD10566@lst.de> From: Robin Murphy Message-ID: <2b98d7b2-bf74-ccc9-881a-a91e2c9949c3@arm.com> Date: Thu, 27 Sep 2018 16:38:31 +0100 MIME-Version: 1.0 In-Reply-To: <20180927153028.GD10566@lst.de> Content-Type: text/plain; charset=utf-8; format=flowed List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 27/09/18 16:30, Christoph Hellwig wrote: > On Thu, Sep 27, 2018 at 03:30:20PM +0100, Robin Murphy wrote: >>> +static gfp_t __dma_direct_optimal_gfp_mask(struct device *dev, u64 >>> dma_mask, >>> + u64 *phys_mask) >>> +{ >>> + if (force_dma_unencrypted()) >>> + *phys_mask = __dma_to_phys(dev, dma_mask); >>> + else >>> + *phys_mask = dma_to_phys(dev, dma_mask); >> >> Maybe make phys_to_dma_direct() take u64 instead of phys_addr_t so we can >> reuse it here? > > This is a dma_to_phys and not a phys_to_dma. Ugh, clearly it's time to stop reviewing patches for today... sorry :( Robin.