linux-kernel - Re: [PATCH 2/2] drm/vkms: Update testing with IGT IGT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1933ce64-af94-4605-912e-01e6c9da93b9@bootlin.com>
Date: Tue, 4 Nov 2025 11:50:09 +0100
From: Louis Chauvet <louis.chauvet@...tlin.com>
To: José Expósito <jose.exposito89@...il.com>
Cc: hamohammed.sa@...il.com, simona@...ll.ch, melissa.srw@...il.com,
 airlied@...il.com, maarten.lankhorst@...ux.intel.com, mripard@...nel.org,
 tzimmermann@...e.de, corbet@....net, dri-devel@...ts.freedesktop.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] drm/vkms: Update testing with IGT IGT_DEVICE



Le 24/10/2025 à 13:00, José Expósito a écrit :
> VKMS is no longer in the platform bus, instead, it is in the faux bus.
> 
> In addition, when present, IGT picks hardware drivers instead of virtual
> drivers, like VKMS or vgem, if they are not forced.
> 
> Update the documentation to use IGT_FORCE_DRIVER instead of IGT_DEVICE.
> 
> Signed-off-by: José Expósito <jose.exposito89@...il.com>

Reviewed-by: Louis Chauvet <louis.chauvet@...tlin.com>

> ---
>   Documentation/gpu/vkms.rst | 19 ++++++++-----------
>   1 file changed, 8 insertions(+), 11 deletions(-)
> 
> diff --git a/Documentation/gpu/vkms.rst b/Documentation/gpu/vkms.rst
> index d8c445c417b7..1e79e62a6bc4 100644
> --- a/Documentation/gpu/vkms.rst
> +++ b/Documentation/gpu/vkms.rst
> @@ -159,26 +159,23 @@ To return to graphical mode, do::
>   
>     sudo systemctl isolate graphical.target
>   
> -Once you are in text only mode, you can run tests using the --device switch
> -or IGT_DEVICE variable to specify the device filter for the driver we want
> -to test. IGT_DEVICE can also be used with the run-tests.sh script to run the
> +Once you are in text only mode, you can run tests using the IGT_FORCE_DRIVER
> +variable to specify the device filter for the driver we want to test.
> +IGT_FORCE_DRIVER can also be used with the run-tests.sh script to run the
>   tests for a specific driver::
>   
> -  sudo ./build/tests/<name of test> --device "sys:/sys/devices/platform/vkms"
> -  sudo IGT_DEVICE="sys:/sys/devices/platform/vkms" ./build/tests/<name of test>
> -  sudo IGT_DEVICE="sys:/sys/devices/platform/vkms" ./scripts/run-tests.sh -t <name of test>
> +  sudo IGT_FORCE_DRIVER="vkms" ./build/tests/<name of test>
> +  sudo IGT_FORCE_DRIVER="vkms" ./scripts/run-tests.sh -t <name of test>
>   
>   For example, to test the functionality of the writeback library,
>   we can run the kms_writeback test::
>   
> -  sudo ./build/tests/kms_writeback --device "sys:/sys/devices/platform/vkms"
> -  sudo IGT_DEVICE="sys:/sys/devices/platform/vkms" ./build/tests/kms_writeback
> -  sudo IGT_DEVICE="sys:/sys/devices/platform/vkms" ./scripts/run-tests.sh -t kms_writeback
> +  sudo IGT_FORCE_DRIVER="vkms" ./build/tests/kms_writeback
> +  sudo IGT_FORCE_DRIVER="vkms" ./scripts/run-tests.sh -t kms_writeback
>   
>   You can also run subtests if you do not want to run the entire test::
>   
> -  sudo ./build/tests/kms_flip --run-subtest basic-plain-flip --device "sys:/sys/devices/platform/vkms"
> -  sudo IGT_DEVICE="sys:/sys/devices/platform/vkms" ./build/tests/kms_flip --run-subtest basic-plain-flip
> +  sudo IGT_FORCE_DRIVER="vkms" ./build/tests/kms_flip --run-subtest basic-plain-flip
>   
>   Testing With KUnit
>   ==================

-- 
--
Louis Chauvet, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com