From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 5/9] PCI: host: brcmstb: add dma-ranges for inbound traffic Date: Fri, 20 Oct 2017 18:17:19 +0200 Message-ID: <20171020161719.GA6247@lst.de> References: <20171017081422.GA19475@lst.de> <20171018065316.GA11183@lst.de> <20171019091644.GA14983@lst.de> <20171020073730.GA12937@lst.de> <20171020145752.GA4694@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-pci-owner@vger.kernel.org To: Jim Quinlan Cc: Christoph Hellwig , Robin Murphy , linux-kernel@vger.kernel.org, Mark Rutland , Linux-MIPS , Florian Fainelli , devicetree@vger.kernel.org, linux-pci , Kevin Cernekee , Will Deacon , Ralf Baechle , Rob Herring , bcm-kernel-feedback-list , Gregory Fong , Catalin Marinas , Bjorn Helgaas , Brian Norris , linux-arm-kernel@lists.infradead.org, Marek Szyprowski , iommu@lists.linux-foun List-Id: iommu@lists.linux-foundation.org On Fri, Oct 20, 2017 at 11:27:41AM -0400, Jim Quinlan wrote: > memc0-a@[ 0....3fffefff] <=> pci@[ 0....3fffefff] > memc0-b@[100000000...13fffefff] <=> pci@[ 40000000....7fffefff] > memc1-a@[ 40000000....7fffefff] <=> pci@[ 80000000....bfffefff] > memc1-b@[300000000...33fffefff] <=> pci@[ c0000000....ffffefff] > memc2-a@[ 80000000....bfffefff] <=> pci@[100000000...13fffefff] > memc2-b@[c00000000...c3fffffff] <=> pci@[140000000...17fffffff] > > This leaves a one-page gap between phsyical memory regions which would > normally be contiguous. One cannot have a dma alloc that spans any two > regions. This is a drastic step, but I don't see an alternative. > Perhaps I may be missing what you are saying... Ok, IFF we are guranteed to always have a gap between physical memory locations we are fine indeed. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 20 Oct 2017 18:17:26 +0200 (CEST) Received: from verein.lst.de ([213.95.11.211]:39469 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S23992181AbdJTQRTi09ZJ (ORCPT ); Fri, 20 Oct 2017 18:17:19 +0200 Received: by newverein.lst.de (Postfix, from userid 2407) id 3BFE77FC80; Fri, 20 Oct 2017 18:17:19 +0200 (CEST) Date: Fri, 20 Oct 2017 18:17:19 +0200 From: Christoph Hellwig To: Jim Quinlan Cc: Christoph Hellwig , Robin Murphy , linux-kernel@vger.kernel.org, Mark Rutland , Linux-MIPS , Florian Fainelli , devicetree@vger.kernel.org, linux-pci , Kevin Cernekee , Will Deacon , Ralf Baechle , Rob Herring , bcm-kernel-feedback-list , Gregory Fong , Catalin Marinas , Bjorn Helgaas , Brian Norris , linux-arm-kernel@lists.infradead.org, Marek Szyprowski , iommu@lists.linux-foundation.org Subject: Re: [PATCH 5/9] PCI: host: brcmstb: add dma-ranges for inbound traffic Message-ID: <20171020161719.GA6247@lst.de> References: <20171017081422.GA19475@lst.de> <20171018065316.GA11183@lst.de> <20171019091644.GA14983@lst.de> <20171020073730.GA12937@lst.de> <20171020145752.GA4694@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 60510 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: hch@lst.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Fri, Oct 20, 2017 at 11:27:41AM -0400, Jim Quinlan wrote: > memc0-a@[ 0....3fffefff] <=> pci@[ 0....3fffefff] > memc0-b@[100000000...13fffefff] <=> pci@[ 40000000....7fffefff] > memc1-a@[ 40000000....7fffefff] <=> pci@[ 80000000....bfffefff] > memc1-b@[300000000...33fffefff] <=> pci@[ c0000000....ffffefff] > memc2-a@[ 80000000....bfffefff] <=> pci@[100000000...13fffefff] > memc2-b@[c00000000...c3fffffff] <=> pci@[140000000...17fffffff] > > This leaves a one-page gap between phsyical memory regions which would > normally be contiguous. One cannot have a dma alloc that spans any two > regions. This is a drastic step, but I don't see an alternative. > Perhaps I may be missing what you are saying... Ok, IFF we are guranteed to always have a gap between physical memory locations we are fine indeed. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Date: Fri, 20 Oct 2017 18:17:19 +0200 From: Christoph Hellwig To: Jim Quinlan Subject: Re: [PATCH 5/9] PCI: host: brcmstb: add dma-ranges for inbound traffic Message-ID: <20171020161719.GA6247@lst.de> References: <20171017081422.GA19475@lst.de> <20171018065316.GA11183@lst.de> <20171019091644.GA14983@lst.de> <20171020073730.GA12937@lst.de> <20171020145752.GA4694@lst.de> MIME-Version: 1.0 In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , Linux-MIPS , Florian Fainelli , devicetree@vger.kernel.org, linux-pci , Kevin Cernekee , Will Deacon , linux-kernel@vger.kernel.org, Ralf Baechle , iommu@lists.linux-foundation.org, Rob Herring , bcm-kernel-feedback-list , Gregory Fong , Catalin Marinas , Bjorn Helgaas , Brian Norris , Robin Murphy , Christoph Hellwig , linux-arm-kernel@lists.infradead.org, Marek Szyprowski Content-Type: text/plain; charset="us-ascii" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+bjorn=helgaas.com@lists.infradead.org List-ID: On Fri, Oct 20, 2017 at 11:27:41AM -0400, Jim Quinlan wrote: > memc0-a@[ 0....3fffefff] <=> pci@[ 0....3fffefff] > memc0-b@[100000000...13fffefff] <=> pci@[ 40000000....7fffefff] > memc1-a@[ 40000000....7fffefff] <=> pci@[ 80000000....bfffefff] > memc1-b@[300000000...33fffefff] <=> pci@[ c0000000....ffffefff] > memc2-a@[ 80000000....bfffefff] <=> pci@[100000000...13fffefff] > memc2-b@[c00000000...c3fffffff] <=> pci@[140000000...17fffffff] > > This leaves a one-page gap between phsyical memory regions which would > normally be contiguous. One cannot have a dma alloc that spans any two > regions. This is a drastic step, but I don't see an alternative. > Perhaps I may be missing what you are saying... Ok, IFF we are guranteed to always have a gap between physical memory locations we are fine indeed. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel From mboxrd@z Thu Jan 1 00:00:00 1970 From: hch@lst.de (Christoph Hellwig) Date: Fri, 20 Oct 2017 18:17:19 +0200 Subject: [PATCH 5/9] PCI: host: brcmstb: add dma-ranges for inbound traffic In-Reply-To: References: <20171017081422.GA19475@lst.de> <20171018065316.GA11183@lst.de> <20171019091644.GA14983@lst.de> <20171020073730.GA12937@lst.de> <20171020145752.GA4694@lst.de> Message-ID: <20171020161719.GA6247@lst.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Oct 20, 2017 at 11:27:41AM -0400, Jim Quinlan wrote: > memc0-a@[ 0....3fffefff] <=> pci@[ 0....3fffefff] > memc0-b@[100000000...13fffefff] <=> pci@[ 40000000....7fffefff] > memc1-a@[ 40000000....7fffefff] <=> pci@[ 80000000....bfffefff] > memc1-b@[300000000...33fffefff] <=> pci@[ c0000000....ffffefff] > memc2-a@[ 80000000....bfffefff] <=> pci@[100000000...13fffefff] > memc2-b@[c00000000...c3fffffff] <=> pci@[140000000...17fffffff] > > This leaves a one-page gap between phsyical memory regions which would > normally be contiguous. One cannot have a dma alloc that spans any two > regions. This is a drastic step, but I don't see an alternative. > Perhaps I may be missing what you are saying... Ok, IFF we are guranteed to always have a gap between physical memory locations we are fine indeed.