| Age | Commit message (Collapse) | Author |
|---|
|
Many of the selftests try to completely fill global resources; resources
that are presumed available for bringing up the display. Avoid the
contention by simply not bringing up the display!
This does limit the effectiveness of selftesting to GEM for the
time being. To exercise KMS from selftests we would essentially have to
always mock the displays.
References: https://bugs.freedesktop.org/show_bug.cgi?id=103718
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
|
|
This reverts commit 7ab5c97924bf971a348ff4a1768da624ba2f564c.
|
|
Even when the running kernel does not support selftests, make subtest
enumeration list known kselftests. The list is generated using
selftest listing headers copied from the kernel.
If the running kernel gains new selftest subtests, they are listed
even without copying the headers over and rebuilding IGT.
v2: Use correct names for the testcases
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
|
|
"Live" selftesting of i915.ko happens during device probing which eats
the error code and does not propagate it back to module loading.
Workaround this by writing the error code back to the module parameter
and probing it after a "successful" install.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
