From: Zack Rusin <zack@kde.org>
To: dri-devel@lists.freedesktop.org
Cc: krastevm@vmware.com, banackm@vmware.com, mombasawalam@vmware.com
Subject: [PATCH v2 00/16] drm/vmwgfx: fb, cursors and hashtable refactor
Date: Wed, 19 Oct 2022 23:41:15 -0400 [thread overview]
Message-ID: <20221020034131.491973-1-zack@kde.org> (raw)
From: Zack Rusin <zackr@vmware.com>
v2: Fix LKP and sparse reported issues
This is a bit larger series than usual but these are all connected in
various ways. The most important changes around everything is centered
include:
- finally getting rid of vmwgfx_hashtab and porting the driver to
linux/hashtable
- cleaning up the cursor mob handling, which fixes a bunch of cursor
issues on kde configs
- removing vmwgfx fb code and porting it to drm fb helpers
- removing vmwgfx faked vblank handling
The rest is largely support code to make the transition easier (with some
igt fixes to get more of it running for regression testing). The result
is removal of over 1000loc with no loss in functionality.
Maaz Mombasawala (5):
drm/vmwgfx: Refactor resource manager's hashtable to use
linux/hashtable implementation.
drm/vmwgfx: Remove ttm object hashtable
drm/vmwgfx: Refactor resource validation hashtable to use
linux/hashtable implementation.
drm/vmwgfx: Refactor ttm reference object hashtable to use
linux/hashtable.
drm/vmwgfx : Remove vmwgfx_hashtab
Martin Krastev (1):
drm/vmwgfx: Fix frame-size warning in vmw_mksstat_add_ioctl
Michael Banack (4):
drm/vmwgfx: Clean up cursor mobs
drm/vmwgfx: Start diffing new mob cursors against old ones
drm/vmwgfx: Support cursor surfaces with mob cursor
drm/vmwgfx: Diff cursors when using cmds
Zack Rusin (6):
drm/vmwgfx: Write the driver id registers
drm/vmwgfx: Do not allow invalid bpp's for dumb buffers
drm/vmwgfx: Port the framebuffer code to drm fb helpers
drm/vmwgfx: Remove explicit and broken vblank handling
drm/vmwgfx: Add a mksstat counter for cotable resizes
drm/vmwgfx: Optimize initial sizes of cotables
Documentation/gpu/todo.rst | 11 -
drivers/gpu/drm/vmwgfx/Kconfig | 7 -
drivers/gpu/drm/vmwgfx/Makefile | 4 +-
drivers/gpu/drm/vmwgfx/ttm_object.c | 123 ++-
drivers/gpu/drm/vmwgfx/ttm_object.h | 20 +-
drivers/gpu/drm/vmwgfx/vmwgfx_bo.c | 16 +-
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf_res.c | 62 +-
drivers/gpu/drm/vmwgfx/vmwgfx_cotable.c | 29 +-
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 129 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 49 +-
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 14 +-
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 831 ---------------------
drivers/gpu/drm/vmwgfx/vmwgfx_hashtab.c | 199 -----
drivers/gpu/drm/vmwgfx/vmwgfx_hashtab.h | 83 --
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 639 ++++++++--------
drivers/gpu/drm/vmwgfx/vmwgfx_kms.h | 31 +-
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 8 -
drivers/gpu/drm/vmwgfx/vmwgfx_mksstat.h | 2 +
drivers/gpu/drm/vmwgfx/vmwgfx_msg.c | 55 +-
drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c | 31 +-
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 26 -
drivers/gpu/drm/vmwgfx/vmwgfx_validation.c | 55 +-
drivers/gpu/drm/vmwgfx/vmwgfx_validation.h | 26 +-
23 files changed, 650 insertions(+), 1800 deletions(-)
delete mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_fb.c
delete mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_hashtab.c
delete mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_hashtab.h
--
2.34.1
next reply other threads:[~2022-10-20 3:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 3:41 Zack Rusin [this message]
2022-10-20 3:41 ` [PATCH v2 01/16] drm/vmwgfx: Write the driver id registers Zack Rusin
2022-10-20 3:41 ` [PATCH v2 02/16] drm/vmwgfx: Fix frame-size warning in vmw_mksstat_add_ioctl Zack Rusin
2022-10-20 3:41 ` [PATCH v2 03/16] drm/vmwgfx: Refactor resource manager's hashtable to use linux/hashtable implementation Zack Rusin
2022-10-20 3:41 ` [PATCH v2 04/16] drm/vmwgfx: Remove ttm object hashtable Zack Rusin
2022-10-20 3:41 ` [PATCH v2 05/16] drm/vmwgfx: Refactor resource validation hashtable to use linux/hashtable implementation Zack Rusin
2022-10-20 3:41 ` [PATCH v2 06/16] drm/vmwgfx: Clean up cursor mobs Zack Rusin
2022-10-20 3:41 ` [PATCH v2 07/16] drm/vmwgfx: Start diffing new mob cursors against old ones Zack Rusin
2022-10-20 3:41 ` [PATCH v2 08/16] drm/vmwgfx: Support cursor surfaces with mob cursor Zack Rusin
2022-10-20 3:41 ` [PATCH v2 09/16] drm/vmwgfx: Diff cursors when using cmds Zack Rusin
2022-10-20 3:41 ` [PATCH v2 10/16] drm/vmwgfx: Refactor ttm reference object hashtable to use linux/hashtable Zack Rusin
2022-10-20 3:41 ` [PATCH v2 11/16] drm/vmwgfx: Remove vmwgfx_hashtab Zack Rusin
2022-10-20 3:41 ` [PATCH v2 12/16] drm/vmwgfx: Do not allow invalid bpp's for dumb buffers Zack Rusin
2022-10-20 3:41 ` [PATCH v2 13/16] drm/vmwgfx: Port the framebuffer code to drm fb helpers Zack Rusin
2022-10-20 9:06 ` Thomas Zimmermann
2022-10-20 18:37 ` Zack Rusin
2022-10-21 7:06 ` Thomas Zimmermann
2022-10-20 3:41 ` [PATCH v2 14/16] drm/vmwgfx: Remove explicit and broken vblank handling Zack Rusin
2022-10-20 3:41 ` [PATCH v2 15/16] drm/vmwgfx: Add a mksstat counter for cotable resizes Zack Rusin
2022-10-20 3:41 ` [PATCH v2 16/16] drm/vmwgfx: Optimize initial sizes of cotables Zack Rusin
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=20221020034131.491973-1-zack@kde.org \
--to=zack@kde.org \
--cc=banackm@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=krastevm@vmware.com \
--cc=mombasawalam@vmware.com \
--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