From: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>
To: "Kim, Dongwon" <dongwon.kim@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>
Subject: RE: [PATCH v2 1/2] drm/virtio: .release ops for virtgpu fence release
Date: Mon, 6 Jun 2022 23:54:20 +0000 [thread overview]
Message-ID: <bacc0e91d9e34b289470b5e838b815e9@intel.com> (raw)
In-Reply-To: <20220603211849.27703-2-dongwon.kim@intel.com>
> virtio_gpu_fence_release is added to free virtio-gpu-fence
> upon release of dma_fence.
>
> Cc: Gurchetan Singh <gurchetansingh@chromium.org>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Vivek Kasireddy <vivek.kasireddy@intel.com>
> Signed-off-by: Dongwon Kim <dongwon.kim@intel.com>
> ---
> drivers/gpu/drm/virtio/virtgpu_fence.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/virtio/virtgpu_fence.c b/drivers/gpu/drm/virtio/virtgpu_fence.c
> index f28357dbde35..ba659ac2a51d 100644
> --- a/drivers/gpu/drm/virtio/virtgpu_fence.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_fence.c
> @@ -63,12 +63,20 @@ static void virtio_gpu_timeline_value_str(struct dma_fence *f,
> char *str,
> (u64)atomic64_read(&fence->drv->last_fence_id));
> }
>
> +static void virtio_gpu_fence_release(struct dma_fence *f)
> +{
> + struct virtio_gpu_fence *fence = to_virtio_gpu_fence(f);
> +
> + kfree(fence);
> +}
> +
> static const struct dma_fence_ops virtio_gpu_fence_ops = {
> .get_driver_name = virtio_gpu_get_driver_name,
> .get_timeline_name = virtio_gpu_get_timeline_name,
> .signaled = virtio_gpu_fence_signaled,
> .fence_value_str = virtio_gpu_fence_value_str,
> .timeline_value_str = virtio_gpu_timeline_value_str,
> + .release = virtio_gpu_fence_release,
Acked-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
> };
>
> struct virtio_gpu_fence *virtio_gpu_fence_alloc(struct virtio_gpu_device *vgdev,
> --
> 2.20.1
next prev parent reply other threads:[~2022-06-06 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 21:18 [PATCH v2 0/2] drm/virtio: fence handling in case of multi scanouts Dongwon Kim
2022-06-03 21:18 ` [PATCH v2 1/2] drm/virtio: .release ops for virtgpu fence release Dongwon Kim
2022-06-06 23:54 ` Kasireddy, Vivek [this message]
2022-06-03 21:18 ` [PATCH v2 2/2] drm/virtio: fence created per cursor/plane update Dongwon Kim
2022-06-07 0:23 ` Kasireddy, Vivek
2022-06-09 4:24 ` Gerd Hoffmann
2022-06-14 19:17 ` Dongwon Kim
2022-06-15 6:09 ` Kasireddy, Vivek
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=bacc0e91d9e34b289470b5e838b815e9@intel.com \
--to=vivek.kasireddy@intel.com \
--cc=dongwon.kim@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=kraxel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.