From: Thierry Reding <thierry.reding@gmail.com>
To: Janne Grunau <j@jannau.net>
Cc: Rob Herring <robh+dt@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Nicolin Chen <nicolinc@nvidia.com>,
Krishna Reddy <vdumpa@nvidia.com>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Sameer Pujar <spujar@nvidia.com>,
devicetree@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-tegra@vger.kernel.org, asahi@lists.linux.dev
Subject: Re: [PATCH v5 2/5] iommu: Implement of_iommu_get_resv_regions()
Date: Wed, 18 May 2022 14:42:38 +0200 [thread overview]
Message-ID: <YoTpvpHcB5j5x1Gn@orome> (raw)
In-Reply-To: <20220515111038.GE26732@jannau.net>
[-- Attachment #1: Type: text/plain, Size: 4836 bytes --]
On Sun, May 15, 2022 at 01:10:38PM +0200, Janne Grunau wrote:
> On 2022-05-12 21:00:49 +0200, 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.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > 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 | 90 ++++++++++++++++++++++++++++++++++++++++
> > include/linux/of_iommu.h | 8 ++++
> > 2 files changed, 98 insertions(+)
> >
> > diff --git a/drivers/iommu/of_iommu.c b/drivers/iommu/of_iommu.c
> > index 5696314ae69e..9e341b5e307f 100644
> > --- a/drivers/iommu/of_iommu.c
> > +++ b/drivers/iommu/of_iommu.c
> > @@ -11,12 +11,15 @@
> > #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>
> > #include <linux/slab.h>
> > #include <linux/fsl/mc.h>
> >
> > +#include <dt-bindings/reserved-memory.h>
> > +
> > #define NO_IOMMU 1
> >
> > static int of_iommu_xlate(struct device *dev,
> > @@ -172,3 +175,90 @@ 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;
>
> Adding 'if (!of_device_is_available(it.node)) continue;' here would help
> backwards compatibility. My plan was to add the reserved regions with
> "iommu-addresses" with all zero adresses and sizes with status =
> "disabled" to the devicetree. A bootloader update is required to fill
> those.
Yes, good point. My plan was originally to have the bootloader/firmware
generate these nodes in their entirety, but yeah, prepopulating them and
having firmware just fill in updated values and setting status = "okay"
seems reasonable to me.
> > +
> > + 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) {
> > + const __be32 *end = maps + size / sizeof(__be32);
> > + struct device_node *np;
> > + unsigned int index = 0;
> > + u32 phandle;
> > + int na, ns;
> > +
> > + while (maps < end) {
> > + phys_addr_t start, end;
> > + 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);
>
> alternatively we could handle mappings/reservations with length 0 as
> error and skip them.
I think we could do both.
Thanks for the feedback,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Janne Grunau <j@jannau.net>
Cc: devicetree@vger.kernel.org, Will Deacon <will@kernel.org>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
linux-tegra@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
Sameer Pujar <spujar@nvidia.com>,
asahi@lists.linux.dev
Subject: Re: [PATCH v5 2/5] iommu: Implement of_iommu_get_resv_regions()
Date: Wed, 18 May 2022 14:42:38 +0200 [thread overview]
Message-ID: <YoTpvpHcB5j5x1Gn@orome> (raw)
In-Reply-To: <20220515111038.GE26732@jannau.net>
[-- Attachment #1.1: Type: text/plain, Size: 4836 bytes --]
On Sun, May 15, 2022 at 01:10:38PM +0200, Janne Grunau wrote:
> On 2022-05-12 21:00:49 +0200, 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.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > 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 | 90 ++++++++++++++++++++++++++++++++++++++++
> > include/linux/of_iommu.h | 8 ++++
> > 2 files changed, 98 insertions(+)
> >
> > diff --git a/drivers/iommu/of_iommu.c b/drivers/iommu/of_iommu.c
> > index 5696314ae69e..9e341b5e307f 100644
> > --- a/drivers/iommu/of_iommu.c
> > +++ b/drivers/iommu/of_iommu.c
> > @@ -11,12 +11,15 @@
> > #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>
> > #include <linux/slab.h>
> > #include <linux/fsl/mc.h>
> >
> > +#include <dt-bindings/reserved-memory.h>
> > +
> > #define NO_IOMMU 1
> >
> > static int of_iommu_xlate(struct device *dev,
> > @@ -172,3 +175,90 @@ 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;
>
> Adding 'if (!of_device_is_available(it.node)) continue;' here would help
> backwards compatibility. My plan was to add the reserved regions with
> "iommu-addresses" with all zero adresses and sizes with status =
> "disabled" to the devicetree. A bootloader update is required to fill
> those.
Yes, good point. My plan was originally to have the bootloader/firmware
generate these nodes in their entirety, but yeah, prepopulating them and
having firmware just fill in updated values and setting status = "okay"
seems reasonable to me.
> > +
> > + 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) {
> > + const __be32 *end = maps + size / sizeof(__be32);
> > + struct device_node *np;
> > + unsigned int index = 0;
> > + u32 phandle;
> > + int na, ns;
> > +
> > + while (maps < end) {
> > + phys_addr_t start, end;
> > + 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);
>
> alternatively we could handle mappings/reservations with length 0 as
> error and skip them.
I think we could do both.
Thanks for the feedback,
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-05-18 12:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 19:00 [PATCH v5 0/5] iommu: Support mappings/reservations in reserved-memory regions Thierry Reding
2022-05-12 19:00 ` Thierry Reding
2022-05-12 19:00 ` [PATCH v5 1/5] dt-bindings: reserved-memory: Document iommu-addresses Thierry Reding
2022-05-12 19:00 ` Thierry Reding
2022-05-13 12:33 ` Rob Herring
2022-05-13 12:33 ` Rob Herring
2022-05-15 10:45 ` Janne Grunau
2022-05-15 10:45 ` Janne Grunau
2022-05-18 13:01 ` Thierry Reding
2022-05-18 13:01 ` Thierry Reding
2022-05-12 19:00 ` [PATCH v5 2/5] iommu: Implement of_iommu_get_resv_regions() Thierry Reding
2022-05-12 19:00 ` Thierry Reding
2022-05-13 3:18 ` kernel test robot
2022-05-13 6:13 ` kernel test robot
2022-05-15 11:10 ` Janne Grunau
2022-05-15 11:10 ` Janne Grunau
2022-05-18 12:42 ` Thierry Reding [this message]
2022-05-18 12:42 ` Thierry Reding
2022-05-12 19:00 ` [PATCH v5 3/5] iommu: dma: Use of_iommu_get_resv_regions() Thierry Reding
2022-05-12 19:00 ` Thierry Reding
2022-05-12 19:00 ` [PATCH v5 4/5] iommu/tegra-smmu: Add support for reserved regions Thierry Reding
2022-05-12 19:00 ` Thierry Reding
2022-05-12 19:00 ` [PATCH v5 5/5] iommu/tegra-smmu: Support managed domains Thierry Reding
2022-05-12 19:00 ` Thierry Reding
2022-05-16 18:30 ` Dmitry Osipenko
2022-05-16 18:30 ` Dmitry Osipenko
2022-05-15 10:35 ` [PATCH v5 0/5] iommu: Support mappings/reservations in reserved-memory regions Janne Grunau
2022-05-15 10:35 ` Janne Grunau
2022-05-18 15:29 ` Thierry Reding
2022-05-18 15:29 ` 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=YoTpvpHcB5j5x1Gn@orome \
--to=thierry.reding@gmail.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=asahi@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.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=robin.murphy@arm.com \
--cc=spujar@nvidia.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 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.