From: Robin Murphy <robin.murphy@arm.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Joerg Roedel <joro@8bytes.org>
Cc: Will Deacon <will@kernel.org>, Nicolin Chen <nicolinc@nvidia.com>,
Krishna Reddy <vdumpa@nvidia.com>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Janne Grunau <j@jannau.net>, Sameer Pujar <spujar@nvidia.com>,
devicetree@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-tegra@vger.kernel.org, asahi@lists.linux.dev,
Frank Rowand <frowand.list@gmail.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v8 2/5] iommu: Implement of_iommu_get_resv_regions()
Date: Fri, 9 Sep 2022 11:56:32 +0100 [thread overview]
Message-ID: <cdac209d-16b3-6c95-6387-4ffeed97178c@arm.com> (raw)
In-Reply-To: <20220905170833.396892-3-thierry.reding@gmail.com>
On 2022-09-05 18:08, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> This is an implementation that IOMMU drivers can use to obtain reserved
> memory regions from a device tree node. It uses the reserved-memory DT
> bindings to find the regions associated with a given device. If these
> regions are marked accordingly, identity mappings will be created for
> them in the IOMMU domain that the devices will be attached to.
>
> Cc: Frank Rowand <frowand.list@gmail.com>
> Cc: devicetree@vger.kernel.org
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v8:
> - cleanup set-but-unused variables
>
> Changes in v6:
> - remove reference to now unused dt-bindings/reserved-memory.h include
>
> Changes in v5:
> - update for new "iommu-addresses" device tree bindings
>
> Changes in v4:
> - fix build failure on !CONFIG_OF_ADDRESS
>
> Changes in v3:
> - change "active" property to identity mapping flag that is part of the
> memory region specifier (as defined by #memory-region-cells) to allow
> per-reference flags to be used
>
> Changes in v2:
> - use "active" property to determine whether direct mappings are needed
>
> drivers/iommu/of_iommu.c | 85 ++++++++++++++++++++++++++++++++++++++++
> include/linux/of_iommu.h | 8 ++++
> 2 files changed, 93 insertions(+)
>
> diff --git a/drivers/iommu/of_iommu.c b/drivers/iommu/of_iommu.c
> index 5696314ae69e..6617096ad15f 100644
> --- a/drivers/iommu/of_iommu.c
> +++ b/drivers/iommu/of_iommu.c
> @@ -11,6 +11,7 @@
> #include <linux/module.h>
> #include <linux/msi.h>
> #include <linux/of.h>
> +#include <linux/of_address.h>
> #include <linux/of_iommu.h>
> #include <linux/of_pci.h>
> #include <linux/pci.h>
> @@ -172,3 +173,87 @@ const struct iommu_ops *of_iommu_configure(struct device *dev,
>
> return ops;
> }
> +
> +/**
> + * of_iommu_get_resv_regions - reserved region driver helper for device tree
> + * @dev: device for which to get reserved regions
> + * @list: reserved region list
> + *
> + * IOMMU drivers can use this to implement their .get_resv_regions() callback
> + * for memory regions attached to a device tree node. See the reserved-memory
> + * device tree bindings on how to use these:
> + *
> + * Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
> + */
> +void of_iommu_get_resv_regions(struct device *dev, struct list_head *list)
> +{
> +#if IS_ENABLED(CONFIG_OF_ADDRESS)
> + struct of_phandle_iterator it;
> + int err;
> +
> + of_for_each_phandle(&it, err, dev->of_node, "memory-region", NULL, 0) {
> + struct iommu_resv_region *region;
> + struct resource res;
> + const __be32 *maps;
> + int size;
> +
> + memset(&res, 0, sizeof(res));
> +
> + /*
> + * The "reg" property is optional and can be omitted by reserved-memory regions
> + * that represent reservations in the IOVA space, which are regions that should
> + * not be mapped.
> + */
> + if (of_find_property(it.node, "reg", NULL)) {
> + err = of_address_to_resource(it.node, 0, &res);
> + if (err < 0) {
> + dev_err(dev, "failed to parse memory region %pOF: %d\n",
> + it.node, err);
> + continue;
> + }
> + }
> +
> + maps = of_get_property(it.node, "iommu-addresses", &size);
> + if (maps) {
Nit: "if (!maps) continue;" and save some indentation.
> + const __be32 *end = maps + size / sizeof(__be32);
> + struct device_node *np;
> + u32 phandle;
> + int na, ns;
> +
> + while (maps < end) {
> + phys_addr_t start;
> + size_t length;
> +
> + phandle = be32_to_cpup(maps++);
> + np = of_find_node_by_phandle(phandle);
> + na = of_n_addr_cells(np);
> + ns = of_n_size_cells(np);
> +
> + start = of_translate_dma_address(np, maps);
> + length = of_read_number(maps + na, ns);
Nit: these could go inside the if condition.
> +
> + if (np == dev->of_node) {
> + int prot = IOMMU_READ | IOMMU_WRITE;
> + enum iommu_resv_type type;
> +
> + /*
> + * IOMMU regions without an associated physical region
> + * cannot be mapped and are simply reservations.
> + */
> + if (res.end > res.start)
> + type = IOMMU_RESV_DIRECT_RELAXABLE;
There may be reservations that have a PA but are expected to live beyond
boot-time handover, like device firmware or a shared-memory
communication buffer which the kernel driver can't reconfigure, or some
kind of black hole that needs a PA because it's also "no-map" for the
CPUs. Those are not relaxable. Might it be reasonable to expect to infer
this from the compatible, or should we have an additional explicit flag
to distinguish ephemeral boot-time mappings from permanent ones?
Furthermore, we should only use IOMMU_RESV_DIRECT (in either form) if
start and length actually match res here; if not then we should warn
that we're reserving the IOVA space but not actually honouring the
specified mapping (we'd need a new resv_region type for arbitrary
translations).
Thanks,
Robin.
> + else
> + type = IOMMU_RESV_RESERVED;
> +
> + region = iommu_alloc_resv_region(start, length, prot, type);
> + if (region)
> + list_add_tail(®ion->list, list);
> + }
> +
> + maps += na + ns;
> + }
> + }
> + }
> +#endif
> +}
> +EXPORT_SYMBOL(of_iommu_get_resv_regions);
> diff --git a/include/linux/of_iommu.h b/include/linux/of_iommu.h
> index 55c1eb300a86..9a5e6b410dd2 100644
> --- a/include/linux/of_iommu.h
> +++ b/include/linux/of_iommu.h
> @@ -12,6 +12,9 @@ extern const struct iommu_ops *of_iommu_configure(struct device *dev,
> struct device_node *master_np,
> const u32 *id);
>
> +extern void of_iommu_get_resv_regions(struct device *dev,
> + struct list_head *list);
> +
> #else
>
> static inline const struct iommu_ops *of_iommu_configure(struct device *dev,
> @@ -21,6 +24,11 @@ static inline const struct iommu_ops *of_iommu_configure(struct device *dev,
> return NULL;
> }
>
> +static inline void of_iommu_get_resv_regions(struct device *dev,
> + struct list_head *list)
> +{
> +}
> +
> #endif /* CONFIG_OF_IOMMU */
>
> #endif /* __OF_IOMMU_H */
next prev parent reply other threads:[~2022-09-09 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 17:08 [PATCH v8 0/5] iommu: Support mappings/reservations in reserved-memory regions Thierry Reding
2022-09-05 17:08 ` [PATCH v8 1/5] dt-bindings: reserved-memory: Document iommu-addresses Thierry Reding
2022-09-08 22:32 ` Rob Herring
2022-09-09 14:45 ` Janne Grunau
2022-09-09 10:24 ` Robin Murphy
2022-09-05 17:08 ` [PATCH v8 2/5] iommu: Implement of_iommu_get_resv_regions() Thierry Reding
2022-09-09 10:56 ` Robin Murphy [this message]
2022-09-09 15:16 ` Janne Grunau
2022-09-09 16:10 ` Robin Murphy
2022-09-05 17:08 ` [PATCH v8 3/5] iommu: dma: Use of_iommu_get_resv_regions() Thierry Reding
2022-09-05 17:08 ` [PATCH v8 4/5] iommu/tegra-smmu: Add support for reserved regions Thierry Reding
2022-09-05 17:08 ` [PATCH v8 5/5] iommu/tegra-smmu: Support managed domains Thierry Reding
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=cdac209d-16b3-6c95-6387-4ffeed97178c@arm.com \
--to=robin.murphy@arm.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=asahi@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=frowand.list@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=j@jannau.net \
--cc=joro@8bytes.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@nvidia.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox