dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: daniel@ffwll.ch, airlied@linux.ie, zackr@vmware.com,
	linux-graphics-maintainer@vmware.com, christian.koenig@amd.com,
	ray.huang@amd.com, mripard@kernel.org,
	maarten.lankhorst@linux.intel.com, sam@ravnborg.org
Cc: Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org
Subject: [PATCH v2 0/3] drm: Make DRM hashtable legacy
Date: Mon, 29 Nov 2021 10:48:38 +0100	[thread overview]
Message-ID: <20211129094841.22499-1-tzimmermann@suse.de> (raw)

Clean up the last non-legacy users of DRM's hashtable code and put
the code behind CONFIG_DRM_LEGACY.

TTM only includes the header file, but does not use the hashtable.
The vmwgfx driver uses the hashtable internally. Copy the DRM code
into the driver. A later patchset should probably update vmwgfx to
use Linux' hashtable. Finally, make the core hashtable code legacy.

Built with/without CONFIG_DRM_LEGACY set.

v2:
	* add TODO item for updating vmwgfx (Sam)

Thomas Zimmermann (3):
  drm/ttm: Don't include drm_hashtab.h
  drm/vmwgfx: Copy DRM hash-table code into driver
  drm: Declare hashtable as legacy

 Documentation/gpu/todo.rst                    |  11 +
 drivers/gpu/drm/Makefile                      |   6 +-
 drivers/gpu/drm/drm_hashtab.c                 |  10 +-
 drivers/gpu/drm/drm_legacy.h                  |  40 +++-
 drivers/gpu/drm/vmwgfx/Makefile               |   2 +-
 drivers/gpu/drm/vmwgfx/ttm_object.c           |  52 ++---
 drivers/gpu/drm/vmwgfx/ttm_object.h           |   3 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf_res.c    |  24 +--
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c           |   2 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h           |   6 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c       |   2 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_hashtab.c       | 199 ++++++++++++++++++
 .../gpu/drm/vmwgfx/vmwgfx_hashtab.h           |  54 ++---
 drivers/gpu/drm/vmwgfx/vmwgfx_validation.c    |  22 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_validation.h    |   7 +-
 include/drm/drm_device.h                      |   5 +-
 include/drm/drm_legacy.h                      |  15 +-
 include/drm/ttm/ttm_bo_api.h                  |   1 -
 18 files changed, 358 insertions(+), 103 deletions(-)
 create mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_hashtab.c
 rename include/drm/drm_hashtab.h => drivers/gpu/drm/vmwgfx/vmwgfx_hashtab.h (58%)


base-commit: 6a8f90ec433e2f5de5fc16d7a4839771b7027cc0
--
2.34.0


             reply	other threads:[~2021-11-29  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29  9:48 Thomas Zimmermann [this message]
2021-11-29  9:48 ` [PATCH v2 1/3] drm/ttm: Don't include drm_hashtab.h Thomas Zimmermann
2021-11-29  9:48 ` [PATCH v2 2/3] drm/vmwgfx: Copy DRM hash-table code into driver Thomas Zimmermann
2021-11-29  9:48 ` [PATCH v2 3/3] drm: Declare hashtable as legacy Thomas Zimmermann
2021-11-29 17:42 ` [PATCH v2 0/3] drm: Make DRM hashtable legacy Alex Deucher

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=20211129094841.22499-1-tzimmermann@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@linux.ie \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-graphics-maintainer@vmware.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=ray.huang@amd.com \
    --cc=sam@ravnborg.org \
    --cc=zackr@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox