diff options
authorTomeu Vizoso <tomeu.vizoso@collabora.com>2016-09-01 09:41:35 +0200
committerDaniel Vetter <daniel.vetter@ffwll.ch>2016-09-01 10:41:53 +0200
commit75ac49532a3cd44f2b22d88bab888ae92c411650 (patch)
parent2b2fd56d7e92f134ecaae5c89e20f64dd0f95aa2 (diff)
drm/doc: Add a few words on validation with IGT
Also provide some pointers for building IGT as some kernel hackers might not be that familiar with building stuff on Linux distros. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Cc: Daniel Vetter <daniel.vetter@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: http://patchwork.freedesktop.org/patch/msgid/1472715695-19812-1-git-send-email-tomeu.vizoso@collabora.com
1 files changed, 37 insertions, 0 deletions
diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index 12b47c3..1ba301c 100644
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -156,6 +156,43 @@ other hand, a driver requires shared state between clients which is
visible to user-space and accessible beyond open-file boundaries, they
cannot support render nodes.
+Validating changes with IGT
+There's a collection of tests that aims to cover the whole functionality of
+DRM drivers and that can be used to check that changes to DRM drivers or the
+core don't regress existing functionality. This test suite is called IGT and
+its code can be found in https://cgit.freedesktop.org/drm/igt-gpu-tools/.
+To build IGT, start by installing its build dependencies. In Debian-based
+ # apt-get build-dep intel-gpu-tools
+And in Fedora-based systems::
+ # dnf builddep intel-gpu-tools
+Then clone the repository::
+ $ git clone git://anongit.freedesktop.org/drm/igt-gpu-tools
+Configure the build system and start the build::
+ $ cd igt-gpu-tools && ./autogen.sh && make -j6
+Download the piglit dependency::
+ $ ./scripts/run-tests.sh -d
+And run the tests::
+ $ ./scripts/run-tests.sh -t kms -t core -s
+run-tests.sh is a wrapper around piglit that will execute the tests matching
+the -t options. A report in HTML format will be available in
+./results/html/index.html. Results can be compared with piglit.
VBlank event handling