From: Maaz Mombasawala <maaz.mombasawala@broadcom.com>
To: dri-devel@lists.freedesktop.org
Cc: bcm-kernel-feedback-list@broadcom.com, ian.forbes@broadcom.com,
zack.rusin@broadcom.com,
Maaz Mombasawala <maaz.mombasawala@broadcom.com>
Subject: [PATCH v3 0/5] Fix some issues from igt runs.
Date: Thu, 14 May 2026 15:48:14 -0700 [thread overview]
Message-ID: <20260514224819.3631763-1-maaz.mombasawala@broadcom.com> (raw)
I ran igt-gpu-tools with vmwgfx and fixed some issues I found.
Changes in v3:
- Minor changes so series can apply cleanly on drm-misc-next.
Changes in v2:
- Changes based on Zack's comments.
- For vrefresh changes, removed stdu specific checks so that test
kms_invalid_mode@overflow-vrefresh passes with sou and ldu displays.
For ttm ref changes, fixed a ref leak in ttm_prime_fd_to_handle()
which fixes a memleak in test vmw_prime@tri-map-dmabuf and removed
release callback for dumb buffer surface since the gem buffer will
handle release of the surface.
Added commit to remove duplicate functions in vmwgfx_bo.h.
Maaz Mombasawala (5):
drm/vmwgfx: Add some checks to vmw_cursor_plane_atomic_update
drm/vmwgfx: Check vrefresh in drm_mode_setcrtc.
drm/vmwgfx: Reserve ttm object before resv usage
drm/vmwgfx: Change ttm refs for dumb buffers.
drm/vmwgfx: Remove duplicates in vmwgfx_bo.h
drivers/gpu/drm/vmwgfx/ttm_object.c | 7 +++--
drivers/gpu/drm/vmwgfx/vmwgfx_bo.c | 6 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_bo.h | 15 ---------
drivers/gpu/drm/vmwgfx/vmwgfx_cotable.c | 4 +--
drivers/gpu/drm/vmwgfx/vmwgfx_cursor_plane.c | 16 +++++++---
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 1 -
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 4 +--
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 32 ++++++++++++++++++--
drivers/gpu/drm/vmwgfx/vmwgfx_kms.h | 9 ++++++
drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_prime.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 12 ++++----
drivers/gpu/drm/vmwgfx/vmwgfx_shader.c | 4 +--
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 12 ++------
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 11 ++++---
drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c | 12 ++++++++
16 files changed, 94 insertions(+), 55 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-14 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 22:48 Maaz Mombasawala [this message]
2026-05-14 22:48 ` [PATCH v3 1/5] drm/vmwgfx: Add some checks to vmw_cursor_plane_atomic_update Maaz Mombasawala
2026-05-16 0:17 ` Claude review: " Claude Code Review Bot
2026-05-14 22:48 ` [PATCH v3 2/5] drm/vmwgfx: Check vrefresh in drm_mode_setcrtc Maaz Mombasawala
2026-05-16 0:17 ` Claude review: " Claude Code Review Bot
2026-05-14 22:48 ` [PATCH v3 3/5] drm/vmwgfx: Reserve ttm object before resv usage Maaz Mombasawala
2026-05-16 0:17 ` Claude review: " Claude Code Review Bot
2026-05-14 22:48 ` [PATCH v3 4/5] drm/vmwgfx: Change ttm refs for dumb buffers Maaz Mombasawala
2026-05-15 5:49 ` Zack Rusin
2026-05-16 0:17 ` Claude review: " Claude Code Review Bot
2026-05-14 22:48 ` [PATCH v3 5/5] drm/vmwgfx: Remove duplicates in vmwgfx_bo.h Maaz Mombasawala
2026-05-16 0:17 ` Claude review: " Claude Code Review Bot
2026-05-16 0:17 ` Claude review: Fix some issues from igt runs Claude Code Review Bot
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=20260514224819.3631763-1-maaz.mombasawala@broadcom.com \
--to=maaz.mombasawala@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ian.forbes@broadcom.com \
--cc=zack.rusin@broadcom.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