From: Srinath Mannam <srinath.mannam@broadcom.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Ray Jui <rjui@broadcom.com>
Cc: bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Srinath Mannam <srinath.mannam@broadcom.com>
Subject: [RFC PATCH 0/3] PCIe Host request to reserve IOVA
Date: Wed, 12 Dec 2018 11:16:06 +0530 [thread overview]
Message-ID: <1544593569-8923-1-git-send-email-srinath.mannam@broadcom.com> (raw)
Few SOCs have limitation that their PCIe host
can't allow few inbound address ranges.
Allowed inbound address ranges are listed in
dma-ranges DT property and this address ranges
are required to do IOVA mapping.
Remaining address ranges have to be reserved in
IOVA mapping.
PCIe Host driver of those SOCs has to list all
address ranges which have to reserve their IOVA
address into PCIe host bridge resource entry list.
IOMMU framework will reserve these IOVAs while
initializing IOMMU domain.
This patch set is based on Linux-4.19-rc1.
Srinath Mannam (3):
PCI: Add dma-resv window list
iommu/dma: IOVA reserve for PCI host reserve address list
PCI: iproc: Add dma reserve resources to host
drivers/iommu/dma-iommu.c | 8 ++++++
drivers/pci/controller/pcie-iproc.c | 49 +++++++++++++++++++++++++++++++++++++
drivers/pci/probe.c | 3 +++
include/linux/pci.h | 1 +
4 files changed, 61 insertions(+)
--
2.7.4
next reply other threads:[~2018-12-12 5:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 5:46 Srinath Mannam [this message]
2018-12-12 5:46 ` [RFC PATCH 1/3] PCI: Add dma-resv window list Srinath Mannam
2018-12-12 5:46 ` [RFC PATCH 2/3] iommu/dma: IOVA reserve for PCI host reserve address list Srinath Mannam
2018-12-12 5:46 ` [RFC PATCH 3/3] PCI: iproc: Add dma reserve resources to host Srinath Mannam
2018-12-13 6:03 ` poza
2018-12-13 9:17 ` Srinath Mannam
2018-12-13 9:58 ` poza
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=1544593569-8923-1-git-send-email-srinath.mannam@broadcom.com \
--to=srinath.mannam@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjui@broadcom.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