From: Frank Binns <Frank.Binns@imgtec.com>
To: "tzimmermann@suse.de" <tzimmermann@suse.de>,
Matt Coster <Matt.Coster@imgtec.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"mripard@kernel.org" <mripard@kernel.org>
Subject: Re: [PATCH RESEND] drm/imagination: Free pvr_vm_gpuva after unlink
Date: Mon, 2 Sep 2024 07:57:23 +0000 [thread overview]
Message-ID: <55dfb0fe2a3996226e814b6f42014dba76cfa3e1.camel@imgtec.com> (raw)
In-Reply-To: <35867394-d8ce-4698-a8fd-919a018f1583@imgtec.com>
On Fri, 2024-08-30 at 15:07 +0000, Matt Coster wrote:
> This caused a measurable memory leak. Although the individual
> allocations are small, the leaks occurs in a high-usage codepath
> (remapping or unmapping device memory) so they add up quickly.
>
Reviewed-by: Frank Binns <frank.binns@imgtec.com>
> Signed-off-by: Matt Coster <matt.coster@imgtec.com>
> Fixes: ff5f643de0bf ("drm/imagination: Add GEM and VM related code")
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/imagination/pvr_vm.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/imagination/pvr_vm.c b/drivers/gpu/drm/imagination/pvr_vm.c
> index e59517ba039e..97c0f772ed65 100644
> --- a/drivers/gpu/drm/imagination/pvr_vm.c
> +++ b/drivers/gpu/drm/imagination/pvr_vm.c
> @@ -114,6 +114,8 @@ struct pvr_vm_gpuva {
> struct drm_gpuva base;
> };
>
> +#define to_pvr_vm_gpuva(va) container_of_const(va, struct pvr_vm_gpuva, base)
> +
> enum pvr_vm_bind_type {
> PVR_VM_BIND_TYPE_MAP,
> PVR_VM_BIND_TYPE_UNMAP,
> @@ -386,6 +388,7 @@ pvr_vm_gpuva_unmap(struct drm_gpuva_op *op, void *op_ctx)
>
> drm_gpuva_unmap(&op->unmap);
> drm_gpuva_unlink(op->unmap.va);
> + kfree(to_pvr_vm_gpuva(op->unmap.va));
>
> return 0;
> }
> @@ -433,6 +436,7 @@ pvr_vm_gpuva_remap(struct drm_gpuva_op *op, void *op_ctx)
> }
>
> drm_gpuva_unlink(op->remap.unmap->va);
> + kfree(to_pvr_vm_gpuva(op->remap.unmap->va));
>
> return 0;
> }
prev parent reply other threads:[~2024-09-02 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 13:13 [PATCH] " Matt Coster
2024-08-30 14:03 ` Frank Binns
2024-08-30 15:07 ` [PATCH RESEND] " Matt Coster
2024-09-02 7:57 ` Frank Binns [this message]
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=55dfb0fe2a3996226e814b6f42014dba76cfa3e1.camel@imgtec.com \
--to=frank.binns@imgtec.com \
--cc=Matt.Coster@imgtec.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--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®