From: Zack Rusin <zack.rusin@broadcom.com>
To: igt-dev@lists.freedesktop.org
Cc: ian.forbes@broadcom.com, martin.krastev@broadcom.com,
maaz.mombasawala@broadcom.com,
Zack Rusin <zack.rusin@broadcom.com>
Subject: [PATCH i-g-t 0/3] Add vmwgfx prime tests
Date: Thu, 9 May 2024 15:15:26 -0400 [thread overview]
Message-ID: <20240509191529.3783796-1-zack.rusin@broadcom.com> (raw)
The following series makes some adjustments for testing prime/dma-buf
on vmwgfx, adds a vmwgfx dedicated test for it and fixes some minor
issues.
Nothing too serioues and everything is contained within the vmwgfx
testing code.
Maaz Mombasawala (1):
tests/vmwgfx: Removing incorrect assert in mob_repeated_unref
Zack Rusin (2):
lib/vmwgfx: Allow using any buffer handle as a surface backing
tests/vmwgfx: Add a prime test
lib/igt_vmwgfx.c | 33 ++-
lib/igt_vmwgfx.h | 12 +-
tests/vmwgfx/meson.build | 3 +-
tests/vmwgfx/vmw_mob_stress.c | 5 +-
tests/vmwgfx/vmw_prime.c | 355 ++++++++++++++++++++++++++++++++
tests/vmwgfx/vmw_ref_count.c | 12 +-
tests/vmwgfx/vmw_surface_copy.c | 8 +-
tests/vmwgfx/vmw_tri.c | 12 +-
8 files changed, 402 insertions(+), 38 deletions(-)
create mode 100644 tests/vmwgfx/vmw_prime.c
--
2.40.1
next reply other threads:[~2024-05-09 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 19:15 Zack Rusin [this message]
2024-05-09 19:15 ` [PATCH i-g-t 1/3] tests/vmwgfx: Removing incorrect assert in mob_repeated_unref Zack Rusin
2024-05-13 14:01 ` Kamil Konieczny
2024-05-09 19:15 ` [PATCH i-g-t 2/3] lib/vmwgfx: Allow using any buffer handle as a surface backing Zack Rusin
2024-05-09 19:15 ` [PATCH i-g-t 3/3] tests/vmwgfx: Add a prime test Zack Rusin
2024-05-10 12:29 ` Kamil Konieczny
2024-05-09 20:36 ` ✗ Fi.CI.BAT: failure for Add vmwgfx prime tests Patchwork
2024-05-09 20:48 ` ✓ CI.xeBAT: success " Patchwork
2024-05-10 1:26 ` ✗ CI.xeFULL: failure " Patchwork
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=20240509191529.3783796-1-zack.rusin@broadcom.com \
--to=zack.rusin@broadcom.com \
--cc=ian.forbes@broadcom.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=maaz.mombasawala@broadcom.com \
--cc=martin.krastev@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