1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
This is a collection of tools for development and testing of the Intel DRM
driver. There are many macro-level test suites that get used against our
driver, including xtest, rendercheck, piglit, and oglconform, but failures
from those can be difficult to track down to kernel changes, and many require
complicated build procedures or specific testing environments to get useful
results.
Thus, intel-graphics-tools was a project I started to collect some low-level
tools I intended to build.
benchmarks/
This should be a collection of useful microbenchmarks. The hope is
that people can use these to tune some pieces of DRM code in relevant
ways.
The benchmarks require KMS to be enabled. When run with an X Server
running, they must be run as root to avoid the authentication
requirement.
Note that a few other microbenchmarks are in tests (like gem_gtt_speed).
tests/
This is a set of automated tests to run against the DRM to validate
changes. Hopefully this can cover the relevant cases we need to
worry about, including backwards compatibility.
Run this tests with "make test" as root from this directory. Note that
no other drm clients (X server) may run.
"make test" only runs a default of test usefull for regression testing.
Other tests not run are:
- tests that might hang the gpu, see HANG in Makefile.am
- gem_stress, a stress test suite. Look at the source for all the
various options.
- testdisplay is only run in the default mode. testdisplay has tons of
options to test different kms functionality, again read the source of
the details.
lib/
Common helper functions and headers used by the other tools.
man/
Manpages, unfortunately rather incomplete.
tools/
This is a collection of debugging tools that had previously been
built with the 2D driver but not shipped. Some distros were hacking
up the 2D build to ship them. Instead, here's a separate package for
people debugging the driver.
These tools generally must be run as root, safe for the ones that just
decode dumps.
debugger/
This tool is to be used to do shader debugging. It acts like a
debug server accepting connections from debug clients such as
mesa. The connections is made with unix domain sockets, and at some
point it would be nice if this directory contained a library for
initiating connections with debug clients..
The debugger must be run as root: "sudo debugger/eudb"
|
