From: Bjorn Helgaas <helgaas@kernel.org>
To: Oza Pawandeep <oza.oza@broadcom.com>
Cc: Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux-foundation.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Oza Pawandeep <oza.pawandeep@gmail.com>
Subject: Re: [PATCH v6 2/3] iommu/pci: reserve IOVA for PCI masters
Date: Wed, 17 May 2017 12:11:54 -0500 [thread overview]
Message-ID: <20170517171154.GF31462@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <1494912127-12890-3-git-send-email-oza.oza@broadcom.com>
On Tue, May 16, 2017 at 10:52:06AM +0530, Oza Pawandeep wrote:
> this patch reserves the IOVA for PCI masters.
> ARM64 based SOCs may have scattered memory banks.
> such as iproc based SOC has
>
> <0x00000000 0x80000000 0x0 0x80000000>, /* 2G @ 2G */
> <0x00000008 0x80000000 0x3 0x80000000>, /* 14G @ 34G */
> <0x00000090 0x00000000 0x4 0x00000000>, /* 16G @ 576G */
> <0x000000a0 0x00000000 0x4 0x00000000>; /* 16G @ 640G */
>
> but incoming PCI transcation addressing capability is limited
s/transcation/transaction/
> by host bridge, for example if max incoming window capability
> is 512 GB, then 0x00000090 and 0x000000a0 will fall beyond it.
>
> to address this problem, iommu has to avoid allocating IOVA which
s/iommu/IOMMU/
> are reserved. which inturn does not allocate IOVA if it falls into hole.
s/inturn/in turn/
next prev parent reply other threads:[~2017-05-17 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 5:22 [PATCH v6 0/3] OF/PCI address PCI inbound memory limitations Oza Pawandeep
2017-05-16 5:22 ` [PATCH v6 1/3] of/pci/dma: fix DMA configuration for PCI masters Oza Pawandeep
2017-05-17 17:10 ` Bjorn Helgaas
2017-05-19 1:37 ` Oza Oza
2017-05-17 19:13 ` Arnd Bergmann
2017-05-19 2:58 ` Oza Oza
2017-05-22 16:42 ` Oza Oza
2017-05-16 5:22 ` [PATCH v6 2/3] iommu/pci: reserve IOVA " Oza Pawandeep
2017-05-17 17:11 ` Bjorn Helgaas [this message]
2017-05-19 1:21 ` Oza Oza
2017-05-16 5:22 ` [PATCH v6 3/3] PCI/of fix of_dma_get_range; get PCI specific dma-ranges Oza Pawandeep
2017-05-16 7:41 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170517171154.GF31462@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=oza.oza@broadcom.com \
--cc=oza.pawandeep@gmail.com \
--cc=robin.murphy@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®