Add a couple of simple store dword tests to test memory coherence.
gem_storedw_loop simply executes a batch that continually stores an
incremented value to a target buffer object, checking the results after
each batch completes.
gem_storedw_batches_loop does the same thing, but creates a new command
batch buffer for each iteration, which can exercise the buffer creation
code. This test is based on one from Andrzej Kacprowski from Intel.
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
high level summary of the files:
* debug_rdata - get current state from debug registers. Helpful
when developing the debugger, and could serve some purpose in the
future.
* eudb - the debugger itself
* eviction_macro - generate the proper macro to flush the EU render
cache until I get control flow working
* pre_cpp - an evaluating c preprocesser like thing, to be used before
cpp
* sr - the system routine, exception handler which runs on the EU
* test - a very basic test system routine
* debug.h
This app is required for debug features which seem to (undocumented)
reset themselves if/when the GT goes to sleep.
It is also useful for those doing general debugging or profiling from
userspace when they do not wish to have the GT sleep.
v2: made forcewaked more daemon-like
Cc: Chris Wilson <chris@chris-wilson.co.uk>
In other news: We've been missing a unmapping_mapping_range somewhere
in the kernel. But lazy me never came around to digging up the real
cause.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
As signals cause the syscalls to be interrupted, we often need to clean
up partial state before returning to userspace. Often a source of
unamusing bugs, so encourage gem_stress to provoke them.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
gem_stress -p1 is much more evil than gem_stress -c1, it also manages
to tear appart untiled workloads!
Now duct-taping over it still works (--apply-duct-tape) ... hm.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Parses a trace.dat and works out how long each throttle was and how many
batches retired within that period (and their average duration).
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
When using testdisplay on GM965 and Pineview with LVDS, it will fail to
set a mode because the first unused crtc can't be used for LVDS. So
check the possible_crtcs to make sure the crtc can be used.
Signed-off-by: Hai Lan <hai.lan@intel.com>
Remember the 3D pipeline is much more restricted than the BLT engine,
and we were feeding it buffers much larger than either the
render engine or the sampler could manager.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Gah, in my excitement of reproducing the failure reported by
gem_stress, I missed using fenced relocs for the BLT.
Fortunately, it doesn't affect the presence of the error.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
The decode for A8 is incomplete and died with a segfault. First hide the
segfault, latter fix the pretty printing.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
... and we have a winner: gen3_mixed_blits reproduces the issue Daniel
Vetter originally found. It seems clear that we have some incoherence
between the RENDER and BLT units on gen3 that no amount of MI_FLUSH can
hide. Hmmm....
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
gem_stress is unhappy with tiled render copies on gen3. This is a simple
little test to ensure that a set of pure copies with a working set
larger than the aperture are handled correctly.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
