public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: poza@codeaurora.org
To: Srinath Mannam <srinath.mannam@broadcom.com>
Cc: 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>,
	bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] PCIe Host request to reserve IOVA
Date: Thu, 13 Dec 2018 16:16:59 +0530	[thread overview]
Message-ID: <c85f7eb4740d5d76747d1e9a7212b105@codeaurora.org> (raw)
In-Reply-To: <1544697174-6029-1-git-send-email-srinath.mannam@broadcom.com>

On 2018-12-13 16:02, Srinath Mannam wrote:
> 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.
> 
> Changes from v1:
>   - Addressed Oza review comments.
> 
> 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 | 51 
> ++++++++++++++++++++++++++++++++++++-
>  drivers/pci/probe.c                 |  3 +++
>  include/linux/pci.h                 |  1 +
>  4 files changed, 62 insertions(+), 1 deletion(-)

Looks good to me.

Reviewed-by: Oza Pawandeep <poza@codeaurora.org>

      parent reply	other threads:[~2018-12-13 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 10:32 [PATCH v2 0/3] PCIe Host request to reserve IOVA Srinath Mannam
2018-12-13 10:32 ` [PATCH v2 1/3] PCI: Add dma-resv window list Srinath Mannam
2018-12-13 10:32 ` [PATCH v2 2/3] iommu/dma: IOVA reserve for PCI host reserve address list Srinath Mannam
2018-12-13 10:32 ` [PATCH v2 3/3] PCI: iproc: Add dma reserve resources to host Srinath Mannam
2018-12-13 10:46 ` poza [this message]

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=c85f7eb4740d5d76747d1e9a7212b105@codeaurora.org \
    --to=poza@codeaurora.org \
    --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 \
    --cc=srinath.mannam@broadcom.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