Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965755AbeAJPce (ORCPT + 1 other); Wed, 10 Jan 2018 10:32:34 -0500 Received: from verein.lst.de ([213.95.11.211]:47628 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752835AbeAJPc3 (ORCPT ); Wed, 10 Jan 2018 10:32:29 -0500 Date: Wed, 10 Jan 2018 16:32:26 +0100 From: Christoph Hellwig To: Robin Murphy Cc: Christoph Hellwig , iommu@lists.linux-foundation.org, linux-mips@linux-mips.org, linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, Guan Xuetao , linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, linux-c6x-dev@linux-c6x.org, linux-hexagon@vger.kernel.org, x86@kernel.org, Konrad Rzeszutek Wilk , linux-snps-arc@lists.infradead.org, linux-m68k@lists.linux-m68k.org, patches@groups.riscv.org, linux-metag@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Michal Simek , linux-parisc@vger.kernel.org, linux-cris-kernel@axis.com, linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH 31/33] dma-direct: reject too small dma masks Message-ID: <20180110153226.GE17790@lst.de> References: <20180110080027.13879-1-hch@lst.de> <20180110080027.13879-32-hch@lst.de> <0bcca030-a8da-c34a-a905-707986689f33@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0bcca030-a8da-c34a-a905-707986689f33@arm.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Wed, Jan 10, 2018 at 11:49:34AM +0000, Robin Murphy wrote: >> +#ifdef CONFIG_ZONE_DMA >> + if (mask < DMA_BIT_MASK(ARCH_ZONE_DMA_BITS)) >> + return 0; >> +#else >> + /* >> + * Because 32-bit DMA masks are so common we expect every architecture >> + * to be able to satisfy them - either by not supporting more physical >> + * memory, or by providing a ZONE_DMA32. If neither is the case, the >> + * architecture needs to use an IOMMU instead of the direct mapping. >> + */ >> + if (mask < DMA_BIT_MASK(32)) >> + return 0; > > Do you think it's worth the effort to be a little more accommodating here? > i.e.: > > return dma_max_pfn(dev) >= max_pfn; > > We seem to have a fair few 28-31 bit masks for older hardware which > probably associates with host systems packing equivalently small amounts of > RAM. And those devices don't have a ZONE_DMA? I think we could do something like that, but I'd rather have it as a separate commit with a good explanation. Maybe you can just send on on top of the series?