From: Rob Herring <robh@kernel.org>
To: Wang Xingang <wangxingang5@huawei.com>
Cc: Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Frank Rowand <frowand.list@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux IOMMU <iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
PCI <linux-pci@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
xieyingtai@huawei.com
Subject: Re: [PATCH v3] iommu/of: Fix pci_request_acs() before enumerating PCI devices
Date: Thu, 20 May 2021 09:00:59 -0500 [thread overview]
Message-ID: <CAL_JsqKUjUN2c8XzCoL7xepb5xZHLQktqTSekYva6bGEZ5Sx2g@mail.gmail.com> (raw)
In-Reply-To: <1621495708-40364-1-git-send-email-wangxingang5@huawei.com>
On Thu, May 20, 2021 at 2:28 AM Wang Xingang <wangxingang5@huawei.com> wrote:
>
> From: Xingang Wang <wangxingang5@huawei.com>
>
> When booting with devicetree, the pci_request_acs() is called after the
> enumeration and initialization of PCI devices, thus the ACS is not
> enabled. And ACS should be enabled when IOMMU is detected for the
> PCI host bridge, so add check for IOMMU before probe of PCI host and call
> pci_request_acs() to make sure ACS will be enabled when enumerating PCI
> devices.
>
> Fixes: 6bf6c24720d33 ("iommu/of: Request ACS from the PCI core when
> configuring IOMMU linkage")
> Signed-off-by: Xingang Wang <wangxingang5@huawei.com>
> ---
> drivers/iommu/of_iommu.c | 1 -
> drivers/pci/controller/pci-host-common.c | 17 +++++++++++++++++
> 2 files changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/of_iommu.c b/drivers/iommu/of_iommu.c
> index a9d2df001149..54a14da242cc 100644
> --- a/drivers/iommu/of_iommu.c
> +++ b/drivers/iommu/of_iommu.c
> @@ -205,7 +205,6 @@ const struct iommu_ops *of_iommu_configure(struct device *dev,
> .np = master_np,
> };
>
> - pci_request_acs();
> err = pci_for_each_dma_alias(to_pci_dev(dev),
> of_pci_iommu_init, &info);
> } else {
> diff --git a/drivers/pci/controller/pci-host-common.c b/drivers/pci/controller/pci-host-common.c
> index d3924a44db02..5904ad0bd9ae 100644
> --- a/drivers/pci/controller/pci-host-common.c
> +++ b/drivers/pci/controller/pci-host-common.c
This file is generally only for ECAM compliant hosts. Are those the
only hosts we need to support this? From the looks of dts files with
iommu-map, that would be dropping support in lots of cases.
Perhaps in devm_of_pci_bridge_init() or one of the functions it calls
is the better place.
> @@ -49,6 +49,21 @@ static struct pci_config_window *gen_pci_init(struct device *dev,
> return cfg;
> }
>
> +static void pci_host_enable_acs(struct pci_host_bridge *bridge)
> +{
> + struct device_node *np = bridge->dev.parent->of_node;
> + static bool acs_enabled;
> +
> + if (!np || acs_enabled)
> + return;
> +
> + /* Detect IOMMU and make sure ACS will be enabled */
> + if (of_property_read_bool(np, "iommu-map")) {
> + acs_enabled = true;
> + pci_request_acs();
Given this function just sets a variable, I don't think you need the
static acs_enabled here.
> + }
> +}
> +
> int pci_host_common_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> @@ -81,6 +96,8 @@ int pci_host_common_probe(struct platform_device *pdev)
> bridge->ops = (struct pci_ops *)&ops->pci_ops;
> bridge->msi_domain = true;
>
> + pci_host_enable_acs(bridge);
> +
> return pci_host_probe(bridge);
> }
> EXPORT_SYMBOL_GPL(pci_host_common_probe);
> --
> 2.19.1
>
prev parent reply other threads:[~2021-05-20 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 7:28 [PATCH v3] iommu/of: Fix pci_request_acs() before enumerating PCI devices Wang Xingang
2021-05-20 14:00 ` Rob Herring [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=CAL_JsqKUjUN2c8XzCoL7xepb5xZHLQktqTSekYva6bGEZ5Sx2g@mail.gmail.com \
--to=robh@kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@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=lorenzo.pieralisi@arm.com \
--cc=wangxingang5@huawei.com \
--cc=will@kernel.org \
--cc=xieyingtai@huawei.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;
as well as URLs for NNTP newsgroup(s).