From: Robin Murphy <robin.murphy@arm.com>
To: Jonas Karlman <jonas@kwiboo.se>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>, Heiko Stuebner <heiko@sntech.de>
Cc: Benjamin Gaignard <benjamin.gaignard@collabora.com>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] iommu: rockchip: Allocate tables from all available memory for IOMMU v2
Date: Mon, 19 Jun 2023 15:51:28 +0100 [thread overview]
Message-ID: <092dda67-8751-9e80-304d-05465162cd97@arm.com> (raw)
In-Reply-To: <20230617182540.3091374-3-jonas@kwiboo.se>
On 17/06/2023 7:25 pm, Jonas Karlman wrote:
> IOMMU v2 found in newer Rockchip SoCs, e.g. RK356x and RK3588, support
> placing directory and page tables in up to 40-bit addressable physical
> memory.
>
> Remove the use of GFP_DMA32 flag for IOMMU v2 now that the physical
> address to the directory table is correctly written to DTE_ADDR.
FWIW I'd be tempted to refactor a bit harder since this is closely
coupled to the DMA mask and both could be calculated from a single data
value, but there's absolutely nothing wrong with this approach either.
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
[ In fact if you start down that rabbit-hole, then I think logically it
leads to an even bigger refactor to convert the whole lot to use
dma_alloc_pages() instead ]
> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
> ---
> v3:
> - rework to only affect IOMMU v2
>
> v2:
> - no change
>
> drivers/iommu/rockchip-iommu.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iommu/rockchip-iommu.c b/drivers/iommu/rockchip-iommu.c
> index ae42959bc490..8ff69fbf9f65 100644
> --- a/drivers/iommu/rockchip-iommu.c
> +++ b/drivers/iommu/rockchip-iommu.c
> @@ -99,6 +99,7 @@ struct rk_iommu_ops {
> u32 (*mk_dtentries)(dma_addr_t pt_dma);
> u32 (*mk_ptentries)(phys_addr_t page, int prot);
> u64 dma_bit_mask;
> + gfp_t gfp_flags;
> };
>
> struct rk_iommu {
> @@ -727,7 +728,7 @@ static u32 *rk_dte_get_page_table(struct rk_iommu_domain *rk_domain,
> if (rk_dte_is_pt_valid(dte))
> goto done;
>
> - page_table = (u32 *)get_zeroed_page(GFP_ATOMIC | GFP_DMA32);
> + page_table = (u32 *)get_zeroed_page(GFP_ATOMIC | rk_ops->gfp_flags);
> if (!page_table)
> return ERR_PTR(-ENOMEM);
>
> @@ -1076,7 +1077,7 @@ static struct iommu_domain *rk_iommu_domain_alloc(unsigned type)
> * Each level1 (dt) and level2 (pt) table has 1024 4-byte entries.
> * Allocate one 4 KiB page for each table.
> */
> - rk_domain->dt = (u32 *)get_zeroed_page(GFP_KERNEL | GFP_DMA32);
> + rk_domain->dt = (u32 *)get_zeroed_page(GFP_KERNEL | rk_ops->gfp_flags);
> if (!rk_domain->dt)
> goto err_free_domain;
>
> @@ -1377,6 +1378,7 @@ static struct rk_iommu_ops iommu_data_ops_v1 = {
> .mk_dtentries = &rk_mk_dte,
> .mk_ptentries = &rk_mk_pte,
> .dma_bit_mask = DMA_BIT_MASK(32),
> + .gfp_flags = GFP_DMA32,
> };
>
> static struct rk_iommu_ops iommu_data_ops_v2 = {
> @@ -1384,6 +1386,7 @@ static struct rk_iommu_ops iommu_data_ops_v2 = {
> .mk_dtentries = &rk_mk_dte_v2,
> .mk_ptentries = &rk_mk_pte_v2,
> .dma_bit_mask = DMA_BIT_MASK(40),
> + .gfp_flags = 0,
> };
>
> static const struct of_device_id rk_iommu_dt_ids[] = {
next prev parent reply other threads:[~2023-06-19 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 18:25 [PATCH v3 0/2] iommu: rockchip: Fix directory table address encoding Jonas Karlman
2023-06-17 18:25 ` [PATCH v3 1/2] " Jonas Karlman
2023-06-19 14:32 ` Robin Murphy
2023-06-17 18:25 ` [PATCH v3 2/2] iommu: rockchip: Allocate tables from all available memory for IOMMU v2 Jonas Karlman
2023-06-19 14:51 ` Robin Murphy [this message]
2023-07-14 14:18 ` [PATCH v3 0/2] iommu: rockchip: Fix directory table address encoding Joerg Roedel
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=092dda67-8751-9e80-304d-05465162cd97@arm.com \
--to=robin.murphy@arm.com \
--cc=benjamin.gaignard@collabora.com \
--cc=heiko@sntech.de \
--cc=iommu@lists.linux.dev \
--cc=jonas@kwiboo.se \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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