From: Robin Murphy <robin.murphy@arm.com>
To: Jayachandran C <jchandra@broadcom.com>,
Alex Williamson <alex.williamson@redhat.com>,
iommu@lists.linux-foundation.org
Cc: Bjorn Helgaas <helgaas@kernel.org>, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 1/2] PCI: Add PCI device flag PCI_DEV_FLAGS_DMA_ALIAS_ROOT
Date: Mon, 9 May 2016 11:10:35 +0100 [thread overview]
Message-ID: <5730621B.2050503@arm.com> (raw)
In-Reply-To: <1462700001-30086-1-git-send-email-jchandra@broadcom.com>
On 08/05/16 10:33, Jayachandran C via iommu wrote:
> Add a new flag PCI_DEV_FLAGS_DMA_ALIAS_ROOT to limit the DMA alias
> search to go no further than the bridge where the IOMMU is attached.
>
> This has been added to support Broadcom's Vulcan which has the SMMUv3
> and GIC ITS associated with an intermediate bridge in the PCI topology.
> Traversing to buses above would hit internal glue bridges which will
> change the RID.
Can you not just have the relevant callback function detect the relevant
node and terminate the walk of its own accord? That's what I was aiming
for in this patch for the IOMMU setup:
http://article.gmane.org/gmane.linux.kernel.iommu/12456
Is there some flaw in that approach I've missed?
Robin.
> Update the function pci_for_each_dma_alias() to stop when it see a
> bridge with this flag set.
>
> Signed-off-by: Jayachandran C <jchandra@broadcom.com>
> ---
>
> Here is v2 of the patch, the previous discussion is at
> http://lists.linuxfoundation.org/pipermail/iommu/2016-February/015668.html
>
> v1->v2 changes:
> - dropped the BAR quirk (not needed)
> - moved from using the 'skip' flag for some bridges to using
> similar approach to stop the traversal at the bridge with
> PCI_DEV_FLAGS_DMA_ALIAS_ROOT
>
> Comments and suggestions are welcome
>
> JC.
>
> drivers/pci/search.c | 4 ++++
> include/linux/pci.h | 2 ++
> 2 files changed, 6 insertions(+)
>
> diff --git a/drivers/pci/search.c b/drivers/pci/search.c
> index a20ce7d..3ea9c27 100644
> --- a/drivers/pci/search.c
> +++ b/drivers/pci/search.c
> @@ -56,6 +56,10 @@ int pci_for_each_dma_alias(struct pci_dev *pdev,
>
> tmp = bus->self;
>
> + /* stop at bridge where translation unit is associated */
> + if (tmp->dev_flags & PCI_DEV_FLAGS_DMA_ALIAS_ROOT)
> + return ret;
> +
> /*
> * PCIe-to-PCI/X bridges alias transactions from downstream
> * devices using the subordinate bus number (PCI Express to
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 932ec74..b6f832b 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -176,6 +176,8 @@ enum pci_dev_flags {
> PCI_DEV_FLAGS_NO_PM_RESET = (__force pci_dev_flags_t) (1 << 7),
> /* Get VPD from function 0 VPD */
> PCI_DEV_FLAGS_VPD_REF_F0 = (__force pci_dev_flags_t) (1 << 8),
> + /* a non-root bridge where translation occurs, stop alias search here */
> + PCI_DEV_FLAGS_DMA_ALIAS_ROOT = (__force pci_dev_flags_t) (1 << 9),
> };
>
> enum pci_irq_reroute_variant {
>
next prev parent reply other threads:[~2016-05-09 10:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <linux-pci@vger.kernel.org>
2016-05-08 9:33 ` [PATCH v2 1/2] PCI: Add PCI device flag PCI_DEV_FLAGS_DMA_ALIAS_ROOT Jayachandran C
2016-05-08 9:33 ` [PATCH v2 2/2] PCI: Handle Broadcom Vulcan DMA alias calculation quirk Jayachandran C
2016-06-11 17:24 ` Bjorn Helgaas
2016-06-14 16:10 ` Jayachandran C
2016-05-09 10:10 ` Robin Murphy [this message]
2016-05-11 6:28 ` [PATCH v2 1/2] PCI: Add PCI device flag PCI_DEV_FLAGS_DMA_ALIAS_ROOT Jayachandran C
2016-05-11 14:26 ` Robin Murphy
2016-05-17 11:55 ` Jayachandran C
2016-06-23 5:01 ` Jon Masters
[not found] ` <037404e2-3168-8f99-0bdb-bb929776108e-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-23 12:04 ` Robin Murphy
2016-06-23 12:04 ` Robin Murphy
[not found] ` <576BD031.7090105-5wv7dgnIgG8@public.gmane.org>
2016-06-23 13:19 ` Jon Masters
2016-06-23 13:19 ` Jon Masters
2016-06-24 3:37 ` Bjorn Helgaas
2016-06-24 3:37 ` Bjorn Helgaas
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=5730621B.2050503@arm.com \
--to=robin.murphy@arm.com \
--cc=alex.williamson@redhat.com \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jchandra@broadcom.com \
--cc=linux-pci@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.