Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp172881pxk; Thu, 24 Sep 2020 02:40:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz5/bqzVCbQbHDcR5Cs4NgMysGuYwBNSsnTxu/feQ/4rZvaHf154+/imJxRJCYYMQhiZXKo X-Received: by 2002:a17:906:1644:: with SMTP id n4mr104438ejd.332.1600940425191; Thu, 24 Sep 2020 02:40:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600940425; cv=none; d=google.com; s=arc-20160816; b=y/n0IBUujtUAKq1FrhwTRlEo48GOoXp57lGOmJGD4nPsNd36QG0w3Cn3B3tN6lilvr 8QJ3NIMbgzYldAaV4+nxN8fbazhBuqQ2ca9jb/3LIp+/ooxSwGs7E+AharFMV9KDfuN9 tESXlYVuSG1dbWPA0INRIwhAdpwEb1aDUu7F6L42xDESAhvKUPwMFe0HoZHqp8sJXwFO mDSPkRnTxknsQFuOvLf6QxWQILmGZMezLkkribV7/FYK162KevzTPciKcUqqVst6GqHg habxXB5edTU13apSoK1+Bs0Rn0QtjIIibffuGc5z0U/NvaWKh9uQwNwehas7VTioTx9n PXgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=bsoATDEPKPRiwkLkUw6rl/ai0IMTIgZo6ywMQ8eOmXQ=; b=odEkYDNGB0i8FCx+Mudj83oKe9VtagFczmXZ64DCXtbw1HU7KrodsKjO+X73SG6KZh Dm8R4dIlHAdyguuSWsNu6M+x4tM3T3oQFPEITjIrHkg6sYRf7Aw/qy7pbWnhOEz7+J6y OPjfnN3e6EUMRRdfIEOA6oDE/UDQI0hlIh3TRhYVX5XNktJSBh+bueD3A4b+YHSGGMt4 SyYsXGm2Zde/pEvD/lM/CPwhvbLD7794T9/+L3IJSSx5ivFkJEujQjjGH4zgbvPt5a6R M1cJ6XBXfiZdpWxNnWtZWpO1m4zmRk8Ofl6bIigoSQMXcqS2risFJxTEaw7DHGv9Q9j5 L6gQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w7si1560311ejf.3.2020.09.24.02.40.00; Thu, 24 Sep 2020 02:40:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726847AbgIXJgw (ORCPT + 99 others); Thu, 24 Sep 2020 05:36:52 -0400 Received: from foss.arm.com ([217.140.110.172]:40048 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726614AbgIXJgw (ORCPT ); Thu, 24 Sep 2020 05:36:52 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 9AFC911D4; Thu, 24 Sep 2020 02:36:51 -0700 (PDT) Received: from [10.57.48.76] (unknown [10.57.48.76]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 0343E3F73B; Thu, 24 Sep 2020 02:36:48 -0700 (PDT) Subject: Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables To: Joerg Roedel Cc: Poonam Aggrwal , robh@kernel.org, Joerg Roedel , Arnd Bergmann , Richard Weinberger , Naresh Kamboju , open list , lkft-triage@lists.linaro.org, "open list:IOMMU DRIVERS" , Linux-Next Mailing List , linux-mtd@lists.infradead.org, Miquel Raynal , Suram Suram , masonccyang@mxic.com.tw, Will Deacon , Zhiqiang.Hou@nxp.com References: <20200924090349.GF27174@8bytes.org> <20200924092546.GJ27174@8bytes.org> From: Robin Murphy Message-ID: Date: Thu, 24 Sep 2020 10:36:47 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Thunderbird/78.2.2 MIME-Version: 1.0 In-Reply-To: <20200924092546.GJ27174@8bytes.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-09-24 10:25, Joerg Roedel wrote: > Hi Robin, > > On Thu, Sep 24, 2020 at 10:08:46AM +0100, Robin Murphy wrote: >> This should be fixed by https://lore.kernel.org/linux-iommu/daedc9364a19dc07487e4d07b8768b1e5934abd4.1600700881.git.robin.murphy@arm.com/T/#u >> (already in linux-next). > > Thanks! The question remains why this goes through the dma-mapping tree, > was it caused by a patch there? Yes, the issue was introduced by one of the changes in "dma-mapping: introduce DMA range map, supplanting dma_pfn_offset", so it only existed in the dma-mapping/for-next branch anyway. Robin.