From: Robin Murphy <robin.murphy@arm.com>
To: Oreoluwa Babatunde <oreoluwa.babatunde@oss.qualcomm.com>,
robh@kernel.org, m.szyprowski@samsung.com
Cc: saravanak@google.com, quic_obabatun@quicinc.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux.dev, william.zhang@broadcom.com,
kernel@oss.qualcomm.com, will@kernel.org, djakov@kernel.org
Subject: Re: [PATCH] of: reserved_mem: Restructure call site for dma_contiguous_early_fixup()
Date: Tue, 8 Jul 2025 18:17:10 +0100 [thread overview]
Message-ID: <ceedcc51-7a4e-4da0-bdcd-429e7c212d19@arm.com> (raw)
In-Reply-To: <20250708165627.845295-1-oreoluwa.babatunde@oss.qualcomm.com>
On 08/07/2025 5:56 pm, Oreoluwa Babatunde wrote:
> Restructure the call site for dma_contiguous_early_fixup() to
> where the reserved_mem nodes are being parsed from the DT so that
> dma_mmu_remap[] is populated before dma_contiguous_remap() is called.
>
> Fixes: 8a6e02d0c00e ("of: reserved_mem: Restructure how the reserved memory regions are processed")
> Signed-off-by: Oreoluwa Babatunde <oreoluwa.babatunde@oss.qualcomm.com>
> ---
> drivers/of/of_reserved_mem.c | 14 +++++++++++---
> kernel/dma/contiguous.c | 2 --
> 2 files changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/of/of_reserved_mem.c b/drivers/of/of_reserved_mem.c
> index 77016c0cc296..132d2c66cafc 100644
> --- a/drivers/of/of_reserved_mem.c
> +++ b/drivers/of/of_reserved_mem.c
> @@ -25,6 +25,7 @@
> #include <linux/memblock.h>
> #include <linux/kmemleak.h>
> #include <linux/cma.h>
> +#include <linux/dma-map-ops.h>
>
> #include "of_private.h"
>
> @@ -175,13 +176,17 @@ static int __init __reserved_mem_reserve_reg(unsigned long node,
> base = dt_mem_next_cell(dt_root_addr_cells, &prop);
> size = dt_mem_next_cell(dt_root_size_cells, &prop);
>
> - if (size &&
> - early_init_dt_reserve_memory(base, size, nomap) == 0)
> + if (size && early_init_dt_reserve_memory(base, size, nomap) == 0) {
> + /* Architecture specific contiguous memory fixup. */
> + if (of_flat_dt_is_compatible(node, "shared-dma-pool"))
Surely this is now going to call the fixup for *all* "shared-dma-pool"
reservations, rather than just the ones which are specifically CMA
regions? That seems potentially bad in a number of ways.
Thanks,
Robin.
> + dma_contiguous_early_fixup(base, size);
> +
> pr_debug("Reserved memory: reserved region for node '%s': base %pa, size %lu MiB\n",
> uname, &base, (unsigned long)(size / SZ_1M));
> - else
> + } else {
> pr_err("Reserved memory: failed to reserve memory for node '%s': base %pa, size %lu MiB\n",
> uname, &base, (unsigned long)(size / SZ_1M));
> + }
>
> len -= t_len;
> }
> @@ -472,6 +477,9 @@ static int __init __reserved_mem_alloc_size(unsigned long node, const char *unam
> uname, (unsigned long)(size / SZ_1M));
> return -ENOMEM;
> }
> + /* Architecture specific contiguous memory fixup. */
> + if (of_flat_dt_is_compatible(node, "shared-dma-pool"))
> + dma_contiguous_early_fixup(base, size);
>
> /* Save region in the reserved_mem array */
> fdt_reserved_mem_save_node(node, uname, base, size);
> diff --git a/kernel/dma/contiguous.c b/kernel/dma/contiguous.c
> index 8df0dfaaca18..9e5d63efe7c5 100644
> --- a/kernel/dma/contiguous.c
> +++ b/kernel/dma/contiguous.c
> @@ -480,8 +480,6 @@ static int __init rmem_cma_setup(struct reserved_mem *rmem)
> pr_err("Reserved memory: unable to setup CMA region\n");
> return err;
> }
> - /* Architecture specific contiguous memory fixup. */
> - dma_contiguous_early_fixup(rmem->base, rmem->size);
>
> if (default_cma)
> dma_contiguous_default_area = cma;
next prev parent reply other threads:[~2025-07-08 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 16:56 [PATCH] of: reserved_mem: Restructure call site for dma_contiguous_early_fixup() Oreoluwa Babatunde
2025-07-08 17:17 ` Robin Murphy [this message]
2025-07-08 22:39 ` Oreoluwa Babatunde
2025-07-09 8:38 ` kernel test robot
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=ceedcc51-7a4e-4da0-bdcd-429e7c212d19@arm.com \
--to=robin.murphy@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=kernel@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=oreoluwa.babatunde@oss.qualcomm.com \
--cc=quic_obabatun@quicinc.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=will@kernel.org \
--cc=william.zhang@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 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.