From: Donald Robson <Donald.Robson@imgtec.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>,
Frank Binns <Frank.Binns@imgtec.com>,
Matt Coster <Matt.Coster@imgtec.com>,
"mripard@kernel.org" <mripard@kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"dakr@redhat.com" <dakr@redhat.com>,
Sarah Walker <Sarah.Walker@imgtec.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH drm-misc-next 3/5] drm/imagination: vm: fix drm_gpuvm reference count
Date: Tue, 28 Nov 2023 10:36:10 +0000 [thread overview]
Message-ID: <90f220de5aeb91e5e2dc64ec662ee961414c067f.camel@imgtec.com> (raw)
In-Reply-To: <20231124233650.152653-4-dakr@redhat.com>
Thanks Danilo. It's obvious now you've pointed it out!
Reviewed-by: Donald Robson <donald.robson@imgtec.com>
On Sat, 2023-11-25 at 00:36 +0100, Danilo Krummrich wrote:
> *** CAUTION: This email originates from a source not known to Imagination Technologies. Think before you click a link or open an attachment ***
>
> The driver specific reference count indicates whether the VM should be
> teared down, whereas GPUVM's reference count indicates whether the VM
> structure can finally be freed.
>
> Hence, free the VM structure in pvr_gpuvm_free() and drop the last
> GPUVM reference after tearing down the VM. Generally, this prevents
> lifetime issues such as the VM being freed as long as drm_gpuvm_bo
> structures still hold references to the VM.
>
> Fixes: ff5f643de0bf ("drm/imagination: Add GEM and VM related code")
> Signed-off-by: Danilo Krummrich <dakr@redhat.com>
> ---
> drivers/gpu/drm/imagination/pvr_vm.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/imagination/pvr_vm.c b/drivers/gpu/drm/imagination/pvr_vm.c
> index 1e89092c3dcc..e0d74d9a6190 100644
> --- a/drivers/gpu/drm/imagination/pvr_vm.c
> +++ b/drivers/gpu/drm/imagination/pvr_vm.c
> @@ -64,6 +64,12 @@ struct pvr_vm_context {
> struct drm_gem_object dummy_gem;
> };
>
> +static inline
> +struct pvr_vm_context *to_pvr_vm_context(struct drm_gpuvm *gpuvm)
> +{
> + return container_of(gpuvm, struct pvr_vm_context, gpuvm_mgr);
> +}
> +
> struct pvr_vm_context *pvr_vm_context_get(struct pvr_vm_context *vm_ctx)
> {
> if (vm_ctx)
> @@ -535,7 +541,7 @@ pvr_device_addr_and_size_are_valid(struct pvr_vm_context *vm_ctx,
>
> void pvr_gpuvm_free(struct drm_gpuvm *gpuvm)
> {
> -
> + kfree(to_pvr_vm_context(gpuvm));
> }
>
> static const struct drm_gpuvm_ops pvr_vm_gpuva_ops = {
> @@ -655,12 +661,11 @@ pvr_vm_context_release(struct kref *ref_count)
> WARN_ON(pvr_vm_unmap(vm_ctx, vm_ctx->gpuvm_mgr.mm_start,
> vm_ctx->gpuvm_mgr.mm_range));
>
> - drm_gpuvm_put(&vm_ctx->gpuvm_mgr);
> pvr_mmu_context_destroy(vm_ctx->mmu_ctx);
> drm_gem_private_object_fini(&vm_ctx->dummy_gem);
> mutex_destroy(&vm_ctx->lock);
>
> - kfree(vm_ctx);
> + drm_gpuvm_put(&vm_ctx->gpuvm_mgr);
> }
>
> /**
next prev parent reply other threads:[~2023-11-28 10:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 23:36 [PATCH drm-misc-next 0/5] PowerVR VM fixes Danilo Krummrich
2023-11-24 23:36 ` [PATCH drm-misc-next 1/5] drm/imagination: vm: prevent duplicate drm_gpuvm_bo instances Danilo Krummrich
2023-11-28 10:34 ` [EXTERNAL] " Donald Robson
2023-11-28 13:00 ` (subset) " Maxime Ripard
2023-11-24 23:36 ` [PATCH drm-misc-next 2/5] drm/imagination: vm: check for drm_gpuvm_range_valid() Danilo Krummrich
2023-11-28 10:34 ` [EXTERNAL] " Donald Robson
2023-11-28 13:00 ` (subset) " Maxime Ripard
2023-11-24 23:36 ` [PATCH drm-misc-next 3/5] drm/imagination: vm: fix drm_gpuvm reference count Danilo Krummrich
2023-11-28 10:36 ` Donald Robson [this message]
2023-11-28 13:01 ` (subset) " Maxime Ripard
2023-11-24 23:36 ` [PATCH drm-misc-next 4/5] drm/gpuvm: fall back to drm_exec_lock_obj() Danilo Krummrich
2023-11-24 23:40 ` Danilo Krummrich
2023-11-27 13:52 ` Christian König
2023-11-27 17:50 ` Danilo Krummrich
2023-11-24 23:36 ` [PATCH drm-misc-next 5/5] drm/imagination: vm: make use of GPUVM's drm_exec helper Danilo Krummrich
2023-11-28 10:47 ` [EXTERNAL] " Donald Robson
2023-11-28 19:02 ` Danilo Krummrich
2023-11-27 10:53 ` [PATCH drm-misc-next 0/5] PowerVR VM fixes Frank Binns
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=90f220de5aeb91e5e2dc64ec662ee961414c067f.camel@imgtec.com \
--to=donald.robson@imgtec.com \
--cc=Frank.Binns@imgtec.com \
--cc=Matt.Coster@imgtec.com \
--cc=Sarah.Walker@imgtec.com \
--cc=airlied@gmail.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@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®