From: "Adrián Larumbe" <adrian.larumbe@collabora.com>
To: Akash Goel <akash.goel@arm.com>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
liviu.dudau@arm.com, steven.price@arm.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
nd@arm.com
Subject: Re: [PATCH] drm/panthor: Fix NPD issue on partial unmap of an evicted BO
Date: Tue, 23 Jun 2026 15:14:38 +0100 [thread overview]
Message-ID: <178222407895.3538338.14153540187582641408.b4-reply@b4> (raw)
In-Reply-To: <b85679e3-5ca2-4d36-8675-2b968d97cb5b@arm.com>
On 2026-06-23 13:41:12+01:00, Akash Goel wrote:
> On 6/23/26 13:09, Boris Brezillon wrote:
>
> > On Tue, 23 Jun 2026 12:17:51 +0100
> > Akash Goel <akash.goel@arm.com> wrote:
> >
> >
> > Nah, you're correct, the patching of the drm_gpuva is independent of the
> > adjusted unmap range, so we should be good even if we don't adjust this
> > range for evicted sparse mappings. Sorry for the noise.
>
> No worries. Thanks for confirming.
>
> Since I had a closer look at the code, sorry I have another doubt.
>
> Do we really need the call to 'panthor_fix_sparse_map_offset()' in the
> following code block ?. The 'op->remap.next->gem.offset' would already
> have been patched before.
You're right, it's completely unnecessary. Maybe replace it with a comment that says
the right offset had already been adjusted earlier in the function?
Other than that:
Reviewed-by: Adrián Larumbe <adrian.larumbe@collabora.com>
>
> if (op->remap.next) {
> u64 addr = op->remap.next->va.addr;
> u64 size = unmap_start + unmap_range - op->remap.next->va.addr;
>
> if (!unmap_vma->evicted && size > 0) {
> struct drm_gpuva_op_map map_op = {
> .va.addr = addr,
> .va.range = size,
> .gem.obj = op->remap.next->gem.obj,
> .gem.offset = op->remap.next->gem.offset,
> };
> panthor_fix_sparse_map_offset(&map_op, unmap_vma->flags);
>
> ret = panthor_vm_exec_map_op(vm, unmap_vma->flags, &map_op);
>
> > Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
>
> Sorry I realized that indentation needs to be fixed in my patch.
>
> Will send a v2 and ad your r-b tag.
>
> Best regards
> Akash
next prev parent reply other threads:[~2026-06-23 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 9:24 Akash Goel
2026-06-23 9:53 ` Boris Brezillon
2026-06-23 11:17 ` Akash Goel
2026-06-23 12:09 ` Boris Brezillon
2026-06-23 12:41 ` Akash Goel
2026-06-23 12:55 ` Boris Brezillon
2026-06-23 14:14 ` Adrián Larumbe [this message]
2026-06-23 14:58 ` Akash Goel
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=178222407895.3538338.14153540187582641408.b4-reply@b4 \
--to=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=akash.goel@arm.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nd@arm.com \
--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
all inboxes | Powered by JetHome®