From: Louis Chauvet <louis.chauvet@bootlin.com>
To: "José Expósito" <jose.exposito89@gmail.com>,
igt-dev@lists.freedesktop.org
Cc: zbigniew.kempczynski@intel.com, kamil.konieczny@linux.intel.com,
karthik.b.s@intel.com, Jim Shargo <jshargo@chromium.org>,
Marius Vlad <marius.vlad@collabora.com>
Subject: Re: [PATCH i-g-t v4 01/41] lib/drmtest: Add VKMS as a known driver type
Date: Fri, 5 Sep 2025 22:48:13 +0200 [thread overview]
Message-ID: <b7f169dd-d587-401c-92d9-5d5c8dcdcaf1@bootlin.com> (raw)
In-Reply-To: <20250807074550.6543-2-jose.exposito89@gmail.com>
Le 07/08/2025 à 09:45, José Expósito a écrit :
> As we are going to add VKMS specific tests, allow to check if it is
> available.
>
> Co-developed-by: Jim Shargo <jshargo@chromium.org>
> Signed-off-by: Jim Shargo <jshargo@chromium.org>
> Co-developed-by: Marius Vlad <marius.vlad@collabora.com>
> Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
> Signed-off-by: José Expósito <jose.exposito89@gmail.com>
Reviewed-by: Louis Chauvet <louis.chauvet@bootlin.com>
> ---
> lib/drmtest.c | 21 +++++++++++++++++++++
> lib/drmtest.h | 6 +++++-
> 2 files changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/lib/drmtest.c b/lib/drmtest.c
> index 436b6de78..943ea8dbe 100644
> --- a/lib/drmtest.c
> +++ b/lib/drmtest.c
> @@ -223,6 +223,7 @@ static const struct module {
> { DRIVER_V3D, "v3d" },
> { DRIVER_VC4, "vc4" },
> { DRIVER_VGEM, "vgem" },
> + { DRIVER_VKMS, "vkms" },
> { DRIVER_VMWGFX, "vmwgfx" },
> { DRIVER_XE, "xe" },
> {}
> @@ -295,6 +296,8 @@ static const char *chipset_to_str(int chipset)
> return "xe";
> case DRIVER_VMWGFX:
> return "vmwgfx";
> + case DRIVER_VKMS:
> + return "vkms";
> case DRIVER_ANY:
> return "any";
> default:
> @@ -971,3 +974,21 @@ void igt_require_xe(int fd)
> {
> igt_require(is_xe_device(fd));
> }
> +
> +void igt_require_vkms(void)
> +{
> + /*
> + * Since VKMS can create and destroy virtual drivers at will, instead
> + * look to make sure the driver is installed.
> + */
> + struct stat s = {};
> + int ret;
> + const char *vkms_module_dir = "/sys/module/vkms";
> +
> + ret = stat(vkms_module_dir, &s);
> +
> + igt_require_f(ret == 0, "VKMS stat of %s returned %d (%s)\n",
> + vkms_module_dir, ret, strerror(ret));
> + igt_require_f(S_ISDIR(s.st_mode),
> + "VKMS stat of %s was not a directory\n", vkms_module_dir);
> +}
> diff --git a/lib/drmtest.h b/lib/drmtest.h
> index 27e5a18e2..a9542dde2 100644
> --- a/lib/drmtest.h
> +++ b/lib/drmtest.h
> @@ -55,14 +55,17 @@ int __get_drm_device_name(int fd, char *name, int name_size);
> #define DRIVER_MSM (1 << 6)
> #define DRIVER_XE (1 << 7)
> #define DRIVER_VMWGFX (1 << 8)
> +#define DRIVER_VKMS (1 << 9)
>
> /*
> * Exclude DRVER_VGEM from DRIVER_ANY since if you run on a system
> * with vgem as well as a supported driver, you can end up with a
> * near-100% skip rate if you don't explicitly specify the device,
> * depending on device-load ordering.
> + *
> + * Exclude VKMS to prefer hardware drivers.
> */
> -#define DRIVER_ANY ~(DRIVER_VGEM)
> +#define DRIVER_ANY ~(DRIVER_VGEM | DRIVER_VKMS)
>
> /*
> * Compile friendly enum for i915/xe.
> @@ -135,6 +138,7 @@ void igt_require_i915(int fd);
> void igt_require_nouveau(int fd);
> void igt_require_vc4(int fd);
> void igt_require_xe(int fd);
> +void igt_require_vkms(void);
>
> bool is_amdgpu_device(int fd);
> bool is_i915_device(int fd);
--
Louis Chauvet, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-09-05 20:48 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 7:45 [PATCH i-g-t v4 00/41] VKMS configfs tests José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 01/41] lib/drmtest: Add VKMS as a known driver type José Expósito
2025-08-12 15:33 ` Kamil Konieczny
2025-09-05 20:48 ` Louis Chauvet [this message]
2025-08-07 7:45 ` [PATCH i-g-t v4 02/41] lib/vkms: Add minimal VKMS library and test device default files José Expósito
2025-08-13 13:28 ` Kamil Konieczny
2025-08-14 10:52 ` José Expósito
2025-08-28 10:49 ` Kamil Konieczny
2025-09-05 20:49 ` Louis Chauvet
2025-09-08 11:30 ` Kamil Konieczny
2025-08-07 7:45 ` [PATCH i-g-t v4 03/41] lib/vkms: Allow to enable/disable VKMS devices José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 04/41] tests/vkms_configfs: Test device invalid values José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 05/41] lib/vkms: Test plane default files José Expósito
2025-08-13 13:38 ` Kamil Konieczny
2025-09-05 20:51 ` Louis Chauvet
2025-08-07 7:45 ` [PATCH i-g-t v4 06/41] lib/vkms: Test plane default values José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 07/41] lib/vkms: Test plane invalid values José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 08/41] tests/vkms_configfs: Test plane valid values José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 09/41] lib/vkms: Test CRTC default files José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 10/41] lib/vkms: Test CRTC default values José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 11/41] lib/vkms: Test CRTC invalid values José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 12/41] tests/vkms_configfs: Test CRTC valid values José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 13/41] lib/vkms: Test encoder default files José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 14/41] lib/vkms: Test connector " José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 15/41] lib/vkms: Test connector default values José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 16/41] lib/vkms: Test connector invalid values José Expósito
2025-08-28 10:48 ` Kamil Konieczny
2025-09-05 20:53 ` Louis Chauvet
2025-08-07 7:45 ` [PATCH i-g-t v4 17/41] tests/vkms_configfs: Test connector valid values José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 18/41] lib/vkms: Test attaching planes to CRTCs José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 19/41] lib/vkms: Test attaching encoders " José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 20/41] lib/vkms: Test attaching connectors to encoders José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 21/41] lib/igt_device_scan: Allow to find device by sysname José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 22/41] tests/vkms_configfs: Test enablement without pipeline items José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 23/41] lib/vkms: Create VKMS device from static config José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 24/41] tests/vkms_configfs: Test adding too many planes José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 25/41] tests/vkms_configfs: Test not adding a primary plane José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 26/41] tests/vkms_configfs: Test adding multiple primary planes José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 27/41] tests/vkms_configfs: Test adding multiple cursor planes José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 28/41] tests/vkms_configfs: Test adding a plane without possible CRTCs José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 29/41] tests/vkms_configfs: Test enabling a device without CRTCs José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 30/41] tests/vkms_configfs: Test enabling a device with too many CRTCs José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 31/41] tests/vkms_configfs: Test enabling a device without encoders José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 32/41] tests/vkms_configfs: Test enabling a device with too many encoders José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 33/41] tests/vkms_configfs: Test adding an encoder without possible CRTCs José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 34/41] tests/vkms_configfs: Test adding a CRTC without encoders José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 35/41] tests/vkms_configfs: Test enabling a device without connectors José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 36/41] tests/vkms_configfs: Test enabling a device with too many connectors José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 37/41] lib/vkms: Test changing enabled device planes José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 38/41] lib/vkms: Test changing enabled device CRTCs José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 39/41] lib/vkms: Test changing enabled device encoders José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 40/41] lib/vkms: Test changing enabled device connectors José Expósito
2025-08-07 7:45 ` [PATCH i-g-t v4 41/41] tests/vkms_configfs: Test connector hot-plug José Expósito
2025-08-07 9:02 ` ✓ i915.CI.BAT: success for VKMS configfs tests (rev7) Patchwork
2025-08-07 9:16 ` ✓ Xe.CI.BAT: " Patchwork
2025-08-07 10:16 ` ✗ Xe.CI.Full: failure " Patchwork
2025-08-07 11:08 ` ✗ i915.CI.Full: " Patchwork
2025-09-05 20:55 ` [PATCH i-g-t v4 00/41] VKMS configfs tests Louis Chauvet
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=b7f169dd-d587-401c-92d9-5d5c8dcdcaf1@bootlin.com \
--to=louis.chauvet@bootlin.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jose.exposito89@gmail.com \
--cc=jshargo@chromium.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=karthik.b.s@intel.com \
--cc=marius.vlad@collabora.com \
--cc=zbigniew.kempczynski@intel.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