Age | Commit message (Collapse) | Author |
|
For tests with attempt to hit races and such by running for
relatively long time, it seems that it might be possible to get
by only testing some subtest-engine combinations as long as in
total we still exercise all engines per test.
More precisely, I think that if we view our engines as fast
(!rcs) and a little less fast (others), we group the race
hitting tests in those two camps, we keep the same coverage
by running each subtest against each engine group.
v2: Replace individual engine gem_sync subtests with all
variants. (Chris Wilson)
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Acked-by: Daniel Vetter <daniel.vetter@intel.com>
|
|
Exercise the ABI with a basic test now that we have removed the
defaul engine alias from the engine list.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Acked-by: Daniel Vetter <daniel.vetter@intel.com>
|
|
Default is not an engine but an ABI alias for RCS. Remove it
from the engine list to eliminate redundant subtests and test
passes.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Acked-by: Daniel Vetter <daniel.vetter@intel.com>
|
|
Testing LNCFCMOCS values on non-render engines is tricky. The values in
those registers are lost on RC6, which means that if users of non-render
engines want to see the proper values, they need to obtain a forcewake
and execute something on render (relying on it to restore the values)
before using non-render engine.
Previous version of the test did exactly that - we were relying on the
fact that we're taking forcewake (hidden by intel_register_access_init,
even though the test is not doing any mmio accesses) before iterating
through engines (and render is before other engines, so job done).
I really hope that this is not an ABI and those registers are not used
on non-render in any way. Let's limit testing LNCFCMOCS to render
engine only.
The other non-render issue is that when we're using I915_EXEC_BSD, we
can't be sure which BSD ring we'll end up executing on. Let's
explicitly select BSD1 and BSD2 in our tests.
While we're here, let's also remove the duplicated code and add some
structure by extracting moving more content into subtests.
We're only doing tests that involve "dirtying" the registers for the
render engine - since it's the only one that has those registers in its
context.
v2: Do not skip all BSD engines, test non-default contexts on render
only, change names in CI extended.testlist
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Weinehall <david.weinehall@linux.intel.com>
Cc: Łukasz Kałamarz <lukasz.kalamarz@intel.com>
Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
Reviewed-by: Łukasz Kałamarz <lukasz.kalamarz@intel.com>
|
|
vgem is a nasty test case for various parts of the core as it is a
virtual device with drm_device.dev == NULL; this includes drm_setversion
for example.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Cc: Marta Löfstedt <marta.lofstedt@intel.com>
Cc: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Marta Lofstedt <marta.lofstedt@intel.com>
|
|
.sh files with option parsing and other helpers are gone, as nothing
were using them.
Extended test list updates:
* changed the already converted
* maintained alphabetical ordering
* igt@test_rte_check was removed from the list as it tested the sh
library which is now gone
Cc: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
Cc: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
|
|
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
|
|
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
|
|
Document the test ordering choices in fast-feedback.testlist.
For comments in testlists, piglit commit
commit 0c535186d624071098c10003fdafe8f475ed9ae7
Author: Petri Latvala <petri.latvala@intel.com>
Date: Wed Feb 1 12:57:45 2017 +0200
framework/programs/run.py: Allow comments in test-list files.
is required.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
|
|
The intention of this test is use it to test that the CI system
that runs IGT is collecting the results correctly.
For: VIZ-10281
v2: minor edits
Signed-off-by: Marta Lofstedt <marta.lofstedt@intel.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
|
|
Test list with wider coverage and longer full runtime.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
|
|
Similar to fast-feedback test list. The point of the generic test list is to gather
pass-rate when running generic tests - i.e., tests that don't rely on specific GPUs.
Again, this test list is dynamic and will either shrink or grow over time.
Signed-off-by: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com
|
|
There are several possible relocation methods the kernel uses depending
upon the placement and caching of the buffers. Lots of different code
paths not being covered by BAT - expand the testing to cover them. Even
though there are quite a few paths, individually they are each very
fast.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
Another bug found first in the wild...
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
The purpose of the current placeholder gvt is to reload the module with
gvt enabled. As a reload, it should be last after the basic reload
checks.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Execlists introduces a new wrinkle to filling rings, in that each
context has an independent set of rings. Add the subtest that exercises
filling multiple execlist rings (for the same engine) to BAT.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
The test was removed.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
|
|
A quick test to exercise one module paramter that should disable a chunk
of code usually run at startup and shutdown.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
We want to run the initial set of tests under "pristine startup"
conditions - so that our tests see the hardware as close to the
condition we normally would after booting. This means that we want to
avoid reloading the module until the very last set of tests.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
This test was removed in
commit 7baf4eef259742c9e76bd43d3e1a3849a208abbc
Author: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Date: Wed Dec 21 18:26:54 2016 +0100
kms_cursor_legacy: Make tests less strict.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
|
|
v5:
- reword gem_info to gem_sanitychecks (Chris Wilson)
- remove subgroups/subtests for gem_exec_store and gem_sanitycheck
(Chris Wilson)
v4:
- adjust test to make use of lib/igt_kmod
- replaced SW_FINISH with SET_CACHEING (Chris Wilson)
v3:
- fix passing boolean value as flags to igt_kmod_unload().
v2:
- embedded gem_alive and gem_exec_store into test (Chris Wilson)
- int main() to igt_main (Chris Wilson)
- moved tests/gem_alive -> tools/gem_info (Chris Wilson)
- added to intel-ci/fast-feedback.testlist (Petri Latvala)
- added hda_dynamic_debug() (Petri Latvala)
- renamed from tests/drv_module_reload_basic to tests/drv_module_reload
(all subtests are basic and have been added to fast-feedback.testlist)
Signed-off-by: Marius Vlad <marius.c.vlad@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
Add basic-s4-devices subtests to BAT. At the same time remove basic-s4
from the list, which is atm implicitly disabled via HIBERNATION=n in
kconfig. We would need at least basic S4 coverage provided by
basic-s4-devices, which requires HIBERNATION=y.
v2 (Petri): Don't add s3-devices
Signed-off-by: Imre Deak <imre.deak@intel.com>
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
|
|
Recently a patch ran successfully through BAT that broke 64bit
relocations on a couple of machines. Oops. So lets add a very fast set
of tests to check basic relocation handling.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Add the two basic gem_wait tests to the fast list, together they take a
total of 1s (when correctly functioning).
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
The inter-engine synchronisation (with and without semaphores) is
equally exercised by gem_sync, so leave gem_storedw_loop out of the
"quick" set.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Acked-by: Petri Latvala <petri.latvala@intel.com>
|
|
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
|
|
The test is producing a lot of CI noise.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
|
|
See tests/intel-ci/README for rationale and explanation.
v2: Use the current BAT set for fast-feedback.testlist first
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Acked-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
|