From: Simon Xue <xxm@rock-chips.com>
To: Jonas Karlman <jonas@kwiboo.se>, Midgy BALON <midgy971@gmail.com>
Cc: iommu@lists.linux.dev, joro@8bytes.org, will@kernel.org,
robin.murphy@arm.com, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] iommu/rockchip: fix page table allocation flags for v2 IOMMU
Date: Fri, 3 Apr 2026 12:40:27 +0800 [thread overview]
Message-ID: <5663593b-2c53-4632-ad2c-db9efa8e9ab2@rock-chips.com> (raw)
In-Reply-To: <89ed223d-1a2c-447d-9f21-76969e668855@rock-chips.com>
在 2026/4/1 18:22, Simon Xue 写道:
> Hi Jonas,
>
> 在 2026/4/1 16:41, Jonas Karlman 写道:
>> Hi Simon,
>>
>> On 4/1/2026 9:48 AM, Simon wrote:
>>> Hi Midgy,
>>>
>>> 在 2026/3/31 15:50, Midgy BALON 写道:
>>>> commit 2a7e6400f72b ("iommu: rockchip: Allocate tables from all
>>>> available memory for IOMMU v2") removed GFP_DMA32 from
>>>> iommu_data_ops_v2, reasoning that RK356x and RK3588 IOMMU v2 hardware
>>>> supports up to 40-bit physical addresses for page tables. However, the
>>>> RK3568 IOMMU page-table walker uses a 32-bit AXI bus: it cannot access
>>>> physical addresses above 4 GB regardless of the address encoding
>>>> range.
>>>>
>>>> On boards with more than 4 GB of RAM (e.g. 8 GB LPDDR4X), removing
>>>> GFP_DMA32 causes two distinct failure modes:
>>>>
>>>> 1. Direct allocation above 4 GB: iommu_alloc_pages_sz() may return
>>>> memory above 0x100000000. The hardware page-table walker
>>>> issues a
>>>> bus error trying to dereference those addresses, causing an IOMMU
>>>> fault on the first DMA transaction.
>>> Which IP block is hitting this? We'd like to take a look on our end.
>> I have seen reports that the NPU MMU on RK3568/RK3566 is having some
>> issue using DTE/PTE with >32-bit addresses, maybe it uses a different
>> MMU hw revision or has some hw errata?
>>
>> From my own testing at least the VOP2 MMU on RK3568 (and RK3588) was
>> able to handle 40-bit addressable DTE/PTE, hence the original commit
>> 2a7e6400f72b ("iommu: rockchip: Allocate tables from all available
>> memory for IOMMU v2").
>>
>> As also mentioned in my reply at [1], maybe the NPU MMU has some hw
>> limitation or errata and may need to use a different compatible.
>
> Yes, We are checking internally whether different IOMMU versions
> integrated.
>
> I will share what we find once we have results.
>
We internally checked that the RK356x SoCs integrate two different IOMMU
versions (v1.0 and v2.0), like NPU and ISP use the v1.0 IOMMU.
Both versions can map 40-bit physical pages, but v1.0 does not support
placing the first-level page table above 4 GB.
To fix this, I think we need to land this patch first:
https://lore.kernel.org/all/20260310105303.128859-1-xxm@rock-chips.com/
Then on top of that, we can add a new compatible string to distinguish
the IOMMU versions.
>> [1]
>> https://lore.kernel.org/r/3cd63b3d-1c5e-4a11-856e-c4aeb5d97d55@kwiboo.se/
>>
>> Regards,
>> Jonas
>>
>>>> 2. SWIOTLB bounce-buffer poisoning: without GFP_DMA32, page tables
>>>> land
>>>> above the SWIOTLB window. dma_map_single() with DMA_BIT_MASK(32)
>>>> then bounces them into a buffer below 4 GB.
>>>> rk_dte_get_page_table()
>>>> returns phys_to_virt() of the bounce buffer address; PTEs are
>>>> written
>>>> there; the next dma_sync_single_for_device(DMA_TO_DEVICE)
>>>> copies the
>>>> original (zero) data back over the bounce buffer, silently
>>>> erasing the
>>>> freshly written PTEs. The IOMMU faults because every PTE
>>>> reads as zero.
>>> This probably need a separate patch. One way to fix it would be to
>>> track the
>>> original L2 page table base addresses in struct rk_iommu_domain,
>>> then have rk_dte_get_page_table() return the tracked address instead of
>>> deriving it from the DTE.
>>>
>>>> Restore GFP_DMA32 (and DMA_BIT_MASK(32)) for iommu_data_ops_v2, which
>>>> currently only serves "rockchip,rk3568-iommu" in mainline.
>>>>
>>>> Tested on Radxa ROCK 3B (RK3568, 8 GB LPDDR4X):
>>>> - MobileNetV1 via RKNN: 5.8 ms/inference (IOMMU mode)
>>>> - YOLOv5s 640x640 via RKNN: ~57 ms/inference (IOMMU mode)
>>>> - No IOMMU faults, correct inference results
>>>>
>>>> Fixes: 2a7e6400f72b ("iommu: rockchip: Allocate tables from all
>>>> available memory for IOMMU v2")
>>>> Cc: stable@vger.kernel.org
>>>> Cc: Jonas Karlman <jonas@kwiboo.se>
>>>> Signed-off-by: Midgy BALON <midgy971@gmail.com>
>>>> ---
>>>> drivers/iommu/rockchip-iommu.c | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/iommu/rockchip-iommu.c
>>>> b/drivers/iommu/rockchip-iommu.c
>>>> index 85f3667e797..8b45db29471 100644
>>>> --- a/drivers/iommu/rockchip-iommu.c
>>>> +++ b/drivers/iommu/rockchip-iommu.c
>>>> @@ -1358,8 +1358,8 @@ static struct rk_iommu_ops iommu_data_ops_v2 = {
>>>> .pt_address = &rk_dte_pt_address_v2,
>>>> .mk_dtentries = &rk_mk_dte_v2,
>>>> .mk_ptentries = &rk_mk_pte_v2,
>>>> - .dma_bit_mask = DMA_BIT_MASK(40),
>>>> - .gfp_flags = 0,
>>>> + .dma_bit_mask = DMA_BIT_MASK(32),
>>>> + .gfp_flags = GFP_DMA32,
>>>> };
>>>> static const struct of_device_id rk_iommu_dt_ids[] = {
>>
next prev parent reply other threads:[~2026-04-03 4:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 7:50 Midgy BALON
2026-03-31 7:57 ` Shawn Lin
2026-03-31 18:13 ` Jonas Karlman
2026-04-01 7:48 ` Simon
2026-04-01 8:41 ` Jonas Karlman
2026-04-01 10:22 ` Simon Xue
2026-04-03 4:40 ` Simon Xue [this message]
2026-04-03 14:02 ` Midgy Balon
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=5663593b-2c53-4632-ad2c-db9efa8e9ab2@rock-chips.com \
--to=xxm@rock-chips.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=midgy971@gmail.com \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®