From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Steven Price <steven.price@arm.com>,
kernel@collabora.com, Liviu Dudau <liviu.dudau@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Subject: Re: [PATCH 1/2] drm/panthor: Extend VM locked region for remap case to be a superset
Date: Tue, 7 Apr 2026 08:54:26 +0200 [thread overview]
Message-ID: <20260407085426.26fa3a1e@fedora> (raw)
In-Reply-To: <20260403172116.3424075-1-adrian.larumbe@collabora.com>
On Fri, 3 Apr 2026 18:21:11 +0100
Adrián Larumbe <adrian.larumbe@collabora.com> wrote:
> In the event of an sm_step_remap() that leads to a partial unmap of a
> transparent huge page, the new locked region required by an extended unmap
> might not be a superset of the original one. Then, if it leaves a portion
> of the initially requested one out, the ensuing map will trigger a warning.
>
> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>
> Fixes: 8e7460eac786 ("drm/panthor: Support partial unmaps of huge pages")
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
One suggestion below.
> ---
> drivers/gpu/drm/panthor/panthor_mmu.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c b/drivers/gpu/drm/panthor/panthor_mmu.c
> index fa8b31df85c9..2b96359d3b94 100644
> --- a/drivers/gpu/drm/panthor/panthor_mmu.c
> +++ b/drivers/gpu/drm/panthor/panthor_mmu.c
> @@ -1709,6 +1709,19 @@ static int panthor_vm_lock_region(struct panthor_vm *vm, u64 start, u64 size)
> start + size <= vm->locked_region.start + vm->locked_region.size)
> return 0;
>
> + /* sm_step_remap() may need a locked region that isn't a strict superset
> + * of the original one because of having to extend unmap boundaries beyond
> + * it to deal with partial unmaps of transparent huge pages. What we want
> + * in those cases is to lock the union of both regions.
> + */
> + if (vm->locked_region.size) {
> + u64 end = start + size;
> +
> + start = min(start, vm->locked_region.start);
> + size = max(vm->locked_region.start +
> + vm->locked_region.size, end) - start;
I'd probably go:
u64 end = max(vm->locked_region.start + vm->locked_region.size,
start + size);
start = min(start, vm->locked_region.start);
size = end - start;
> + }
> +
> mutex_lock(&ptdev->mmu->as.slots_lock);
> if (vm->as.id >= 0 && size) {
> /* Lock the region that needs to be updated */
>
> base-commit: fb42964e2a76f68a5fb581d382b5d2be2d5bda9b
next prev parent reply other threads:[~2026-04-07 7:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 17:21 [PATCH 1/2] drm/panthor: Extend VM locked region for remap case to be a superset Adrián Larumbe
2026-04-03 17:21 ` [PATCH 2/2] drm/panthor: Fix outdated function documentation Adrián Larumbe
2026-04-07 6:55 ` Boris Brezillon
2026-04-07 6:54 ` Boris Brezillon [this message]
2026-04-07 10:24 ` [PATCH 1/2] drm/panthor: Extend VM locked region for remap case to be a superset Liviu Dudau
2026-04-07 10:43 ` Boris Brezillon
2026-04-07 11:07 ` Liviu Dudau
2026-04-07 11:33 ` Boris Brezillon
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=20260407085426.26fa3a1e@fedora \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/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