From: Jocelyn Falempe <jfalempe@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
javierm@redhat.com, rrameshbabu@nvidia.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
airlied@gmail.com, simona@ffwll.ch
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/7] drm/client: Deprecate struct drm_client_buffer.gem
Date: Tue, 21 Oct 2025 14:49:36 +0200 [thread overview]
Message-ID: <bbce165c-5abc-4cae-9154-74aba2ca53a0@redhat.com> (raw)
In-Reply-To: <20251020151402.53013-5-tzimmermann@suse.de>
On 20/10/2025 17:04, Thomas Zimmermann wrote:
> The client buffer's framebuffer holds a reference and pointer on
> each of its GEM buffer objects. Thus the field gem in the client-
> buffer struct is not necessary. Deprecated the field and convert
> the client-buffer helpers to use the framebuffer's objects.
>
> In drm_client_buffer_delete(), do a possible vunmap before releasing
> the framebuffer. Otherwise we'd eventually release the framebuffer
> before unmaping its buffer objects.
Thanks, it looks good to me.
Reviewed-by: Jocelyn Falempe <jfalempe@redhat.com>
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
> drivers/gpu/drm/drm_client.c | 20 ++++++++++++--------
> include/drm/drm_client.h | 9 +++------
> 2 files changed, 15 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_client.c b/drivers/gpu/drm/drm_client.c
> index 73ae63f856a0..29ed5f55b5f9 100644
> --- a/drivers/gpu/drm/drm_client.c
> +++ b/drivers/gpu/drm/drm_client.c
> @@ -17,6 +17,7 @@
> #include <drm/drm_fourcc.h>
> #include <drm/drm_framebuffer.h>
> #include <drm/drm_gem.h>
> +#include <drm/drm_gem_framebuffer_helper.h>
> #include <drm/drm_mode.h>
> #include <drm/drm_print.h>
>
> @@ -174,17 +175,17 @@ EXPORT_SYMBOL(drm_client_release);
>
> static void drm_client_buffer_delete(struct drm_client_buffer *buffer)
> {
> + struct drm_gem_object *gem = drm_gem_fb_get_obj(buffer->fb, 0);
> int ret;
>
> + drm_gem_vunmap(gem, &buffer->map);
> +
> ret = drm_mode_rmfb(buffer->client->dev, buffer->fb->base.id, buffer->client->file);
> if (ret)
> drm_err(buffer->client->dev,
> "Error removing FB:%u (%d)\n", buffer->fb->base.id, ret);
>
> - if (buffer->gem) {
> - drm_gem_vunmap(buffer->gem, &buffer->map);
> - drm_gem_object_put(buffer->gem);
> - }
> + drm_gem_object_put(buffer->gem);
>
> kfree(buffer);
> }
> @@ -274,7 +275,7 @@ drm_client_buffer_create(struct drm_client_dev *client, u32 width, u32 height,
> int drm_client_buffer_vmap_local(struct drm_client_buffer *buffer,
> struct iosys_map *map_copy)
> {
> - struct drm_gem_object *gem = buffer->gem;
> + struct drm_gem_object *gem = drm_gem_fb_get_obj(buffer->fb, 0);
> struct iosys_map *map = &buffer->map;
> int ret;
>
> @@ -303,7 +304,7 @@ EXPORT_SYMBOL(drm_client_buffer_vmap_local);
> */
> void drm_client_buffer_vunmap_local(struct drm_client_buffer *buffer)
> {
> - struct drm_gem_object *gem = buffer->gem;
> + struct drm_gem_object *gem = drm_gem_fb_get_obj(buffer->fb, 0);
> struct iosys_map *map = &buffer->map;
>
> drm_gem_vunmap_locked(gem, map);
> @@ -334,9 +335,10 @@ EXPORT_SYMBOL(drm_client_buffer_vunmap_local);
> int drm_client_buffer_vmap(struct drm_client_buffer *buffer,
> struct iosys_map *map_copy)
> {
> + struct drm_gem_object *gem = drm_gem_fb_get_obj(buffer->fb, 0);
> int ret;
>
> - ret = drm_gem_vmap(buffer->gem, &buffer->map);
> + ret = drm_gem_vmap(gem, &buffer->map);
> if (ret)
> return ret;
> *map_copy = buffer->map;
> @@ -355,7 +357,9 @@ EXPORT_SYMBOL(drm_client_buffer_vmap);
> */
> void drm_client_buffer_vunmap(struct drm_client_buffer *buffer)
> {
> - drm_gem_vunmap(buffer->gem, &buffer->map);
> + struct drm_gem_object *gem = drm_gem_fb_get_obj(buffer->fb, 0);
> +
> + drm_gem_vunmap(gem, &buffer->map);
> }
> EXPORT_SYMBOL(drm_client_buffer_vunmap);
>
> diff --git a/include/drm/drm_client.h b/include/drm/drm_client.h
> index db0665263a10..5909664d4d43 100644
> --- a/include/drm/drm_client.h
> +++ b/include/drm/drm_client.h
> @@ -166,12 +166,9 @@ struct drm_client_buffer {
> /**
> * @gem: GEM object backing this buffer
> *
> - * FIXME: The dependency on GEM here isn't required, we could
> - * convert the driver handle to a dma-buf instead and use the
> - * backend-agnostic dma-buf vmap support instead. This would
> - * require that the handle2fd prime ioctl is reworked to pull the
> - * fd_install step out of the driver backend hooks, to make that
> - * final step optional for internal users.
> + * FIXME: The DRM framebuffer holds a reference on its GEM
> + * buffer objects. Do not use this field in new code and
> + * update existing users.
> */
> struct drm_gem_object *gem;
>
next prev parent reply other threads:[~2025-10-21 12:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 15:04 [PATCH 0/7] drm/client: Simply client-buffer interface and implementation Thomas Zimmermann
2025-10-20 15:04 ` [PATCH 1/7] drm/client: Remove pitch from struct drm_client_buffer Thomas Zimmermann
2025-10-21 12:44 ` Jocelyn Falempe
2025-10-20 15:04 ` [PATCH 2/7] drm/client: Move dumb-buffer handling to drm_client_framebuffer_create() Thomas Zimmermann
2025-10-21 12:47 ` Jocelyn Falempe
2025-10-20 15:04 ` [PATCH 3/7] drm/client: Inline drm_client_buffer_addfb() and _rmfb() Thomas Zimmermann
2025-10-21 12:49 ` Jocelyn Falempe
2025-10-20 15:04 ` [PATCH 4/7] drm/client: Deprecate struct drm_client_buffer.gem Thomas Zimmermann
2025-10-21 12:49 ` Jocelyn Falempe [this message]
2025-10-26 9:12 ` kernel test robot
2025-10-20 15:04 ` [PATCH 5/7] drm/client: Remove drm_client_framebuffer_delete() Thomas Zimmermann
2025-10-21 12:50 ` Jocelyn Falempe
2025-10-22 7:00 ` Dan Carpenter
2025-10-20 15:04 ` [PATCH 6/7] drm/client: Create client buffers with drm_client_buffer_create_dumb() Thomas Zimmermann
2025-10-21 12:54 ` Jocelyn Falempe
2025-10-20 15:04 ` [PATCH 7/7] drm/client: Flush client buffers with drm_client_buffer_sync() Thomas Zimmermann
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=bbce165c-5abc-4cae-9154-74aba2ca53a0@redhat.com \
--to=jfalempe@redhat.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rrameshbabu@nvidia.com \
--cc=simona@ffwll.ch \
--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