All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Haneen Mohammed <hamohammed.sa@gmail.com>
Cc: rodrigosiqueiramelo@gmail.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/4] drm/vkms: map/unmap buffers in [prepare/cleanup]_fb hooks
Date: Tue, 10 Jul 2018 10:04:20 +0200	[thread overview]
Message-ID: <20180710080420.GI3008@phenom.ffwll.local> (raw)
In-Reply-To: <3c62d375dc439268e9ea77fb8f3d599ee927a2a6.1531149873.git.hamohammed.sa@gmail.com>

On Mon, Jul 09, 2018 at 06:46:49PM +0300, Haneen Mohammed wrote:
> This patch map/unmap GEM backing memory to kernel address space
> in prepare/cleanup_fb respectively and cache the virtual address
> for later use.
> 
> Signed-off-by: Haneen Mohammed <hamohammed.sa@gmail.com>
> ---
>  drivers/gpu/drm/vkms/vkms_plane.c | 41 +++++++++++++++++++++++++++++++
>  1 file changed, 41 insertions(+)
> 
> diff --git a/drivers/gpu/drm/vkms/vkms_plane.c b/drivers/gpu/drm/vkms/vkms_plane.c
> index f7f63143f6d0..f464eb0e05dd 100644
> --- a/drivers/gpu/drm/vkms/vkms_plane.c
> +++ b/drivers/gpu/drm/vkms/vkms_plane.c
> @@ -9,6 +9,7 @@
>  #include "vkms_drv.h"
>  #include <drm/drm_plane_helper.h>
>  #include <drm/drm_atomic_helper.h>
> +#include <drm/drm_gem_framebuffer_helper.h>
>  
>  static const struct drm_plane_funcs vkms_plane_funcs = {
>  	.update_plane		= drm_atomic_helper_update_plane,
> @@ -30,9 +31,49 @@ static void vkms_primary_plane_update(struct drm_plane *plane,
>  {
>  }
>  
> +static int vkms_prepare_fb(struct drm_plane *plane,
> +			   struct drm_plane_state *state)
> +{
> +	struct drm_gem_object *gem_obj;
> +	struct vkms_gem_object *vkms_obj;
> +
> +	if (!state->fb)
> +		return 0;
> +
> +	gem_obj = drm_gem_fb_get_obj(state->fb, 0);
> +	vkms_obj = container_of(gem_obj, struct vkms_gem_object, gem);
> +	vkms_obj->vaddr = vkms_gem_vmap(gem_obj);
> +
> +	if (!vkms_obj->vaddr)
> +		DRM_INFO("vmap failed\n");
> +
> +	return drm_gem_fb_prepare_fb(plane, state);
> +}
> +
> +static void vkms_cleanup_fb(struct drm_plane *plane,
> +			    struct drm_plane_state *old_state)
> +{
> +	struct drm_gem_object *gem_obj;
> +	struct vkms_gem_object *vkms_obj;
> +
> +	if (!old_state->fb)
> +		return;
> +
> +	gem_obj = drm_gem_fb_get_obj(old_state->fb, 0);
> +	vkms_obj = container_of(gem_obj, struct vkms_gem_object, gem);
> +
> +	if (vkms_obj && vkms_obj->pages) {
> +		vunmap(vkms_obj->vaddr);

Please also clear obj->vaddr here.

> +		drm_gem_put_pages(gem_obj, vkms_obj->pages, false, true);
> +		vkms_obj->pages = NULL;

I think it'd be good to also have a vkms_gem_vunmap helper for this, for
symmetry and prettier code.

There's another issue: cleanup/prepare_fb can be called multiple times on
the same fb. This doesn't really happen for the current vkms case where we
only have 1 plane, but if you have more than one plane you can attach the
same fb to all of them. This means we need a vmap counter (probably best
put into the vkms_gem_v(un)map functions), and only create the actual vmap
when the counter goes from 0 -> 1, and release it only when it goes down
to 0 finally. Usually it's called vmap_use_count or so.

Ofc that needs to be protected by the buffer lock, so you need to rework
your locking a bit and pull it out into the vmap/vunmap functions.

Cheers, Daniel

> +	}
> +}
> +
>  static const struct drm_plane_helper_funcs vkms_primary_helper_funcs = {
>  	.atomic_check		= vkms_plane_atomic_check,
>  	.atomic_update		= vkms_primary_plane_update,
> +	.prepare_fb		= vkms_prepare_fb,
> +	.cleanup_fb		= vkms_cleanup_fb,
>  };
>  
>  struct drm_plane *vkms_plane_init(struct vkms_device *vkmsdev)
> -- 
> 2.17.1
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-07-10  8:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 15:42 [PATCH 0/4] Add infrastructure needed for CRC support Haneen Mohammed
2018-07-09 15:44 ` [PATCH 1/4] drm/vkms: Add functions to map GEM backing storage Haneen Mohammed
2018-07-10  8:00   ` Daniel Vetter
2018-07-10  8:12   ` Chris Wilson
2018-07-10 15:12     ` Haneen Mohammed
2018-07-09 15:46 ` [PATCH 2/4] drm/vkms: map/unmap buffers in [prepare/cleanup]_fb hooks Haneen Mohammed
2018-07-10  8:04   ` Daniel Vetter [this message]
2018-07-09 15:47 ` [PATCH 3/4] drm/vkms: Add atomic_helper_check_plane_state Haneen Mohammed
2018-07-10  8:07   ` Daniel Vetter
2018-07-09 15:48 ` [PATCH 4/4] drm/vkms: subclass CRTC state Haneen Mohammed
2018-07-10  8:10   ` Daniel Vetter
2018-07-10 15:13     ` Haneen Mohammed

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=20180710080420.GI3008@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hamohammed.sa@gmail.com \
    --cc=rodrigosiqueiramelo@gmail.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.