From: Sui Jingfeng <sui.jingfeng@linux.dev>
To: Lucas Stach <l.stach@pengutronix.de>,
Russell King <linux+etnaviv@armlinux.org.uk>,
Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Sui Jingfeng <sui.jingfeng@linux.dev>
Subject: [PATCH v3 0/3] drm/etnaviv: Trivial mmu map and ummap cleanups
Date: Fri, 15 Nov 2024 20:32:43 +0800 [thread overview]
Message-ID: <20241115123246.111346-1-sui.jingfeng@linux.dev> (raw)
The 'sg->offset' denotes the offset into a page in bytes, but under drm
subsystem, there has NO drivers that etnaviv can contact that actually
touch the 'offset' data member of SG anymore. This means that all DMA
addresses that sg_dma_address() gives us will be PAGE_SIZE aligned, in
other words, sg->offset will always equal to 0.
But if 'sg->offset != 0' really could happens, then the current implement
might be not correct. Previous commits[1] fix the 'sg->offset == 0' cases
effectively, below is a simple illustration.
One CPU page Another one CPU page
+----+----+----+----+ +----+----+----+----+
|||||| | |||||| |
+----+----+----+----+ +----+----+----+----+
^ ^ ^ ^
| | | |
| | .----------------' |
| | | .----------------'
| | | |
+----+ +----+ +----+
|||||| |||||| | | GPU pages, each one is SZ_4K
+----+ +----+ +----+
Correct implementation.
--------------------------------------------------------------
One CPU page Another one CPU page
+----+----+----+----+ +----+----+----+----+
|///////////////////| |||||| |
+----+----+----+----+ +----+----+----+----+
^ ^ ^ ^
| | | |
| .------------|---' |
| | .-------|--------'
| | | |
| +----+ |
| |||||| |
| +----+ |
| IOVA | GPUVA range collision if use 'sg_dma_len(sg)'
+----+ +----+-------+ directly to map. Because 'sg_dma_len(sg)' is
|////|/|////////////| frequently larger than SZ_4K.
+----+ +----+-------+
Wrong implementation.
If we map the address range with respect to the size of the backing memory,
it will occupy GPUVA ranges that doesn't belong to. Which results in GPUVA
range collision for different buffers.
Patch 0001 of this series give a fix, patch 0002 and 0003
do trivial cleanup which eliminates unnecessary overheads.
v2 -> v3
* Reword and improve commit message
v1 -> v2
* Reword and fix typos and mistakes
v1 Link: https://patchwork.freedesktop.org/series/140589/
Sui Jingfeng (3):
drm/etnaviv: Drop the offset in page manipulation
drm/etnaviv: Fix the debug log of the etnaviv_iommu_map()
drm/etnaviv: Improve VA, PA, SIZE alignment checking
drivers/gpu/drm/etnaviv/etnaviv_mmu.c | 26 +++++++++++---------------
1 file changed, 11 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2024-11-15 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 12:32 Sui Jingfeng [this message]
2024-11-15 12:32 ` [PATCH v3 1/3] drm/etnaviv: Drop the offset in page manipulation Sui Jingfeng
2024-11-15 12:32 ` [PATCH v3 2/3] drm/etnaviv: Fix the debug log of the etnaviv_iommu_map() Sui Jingfeng
2024-11-15 12:32 ` [PATCH v3 3/3] drm/etnaviv: Improve VA, PA, SIZE alignment checking Sui Jingfeng
2024-12-03 17:44 ` [PATCH v3 0/3] drm/etnaviv: Trivial mmu map and ummap cleanups Lucas Stach
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=20241115123246.111346-1-sui.jingfeng@linux.dev \
--to=sui.jingfeng@linux.dev \
--cc=airlied@gmail.com \
--cc=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
/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®