| Age | Commit message (Collapse) | Author |
|---|
|
Since all the batches start with the same content, we can reuse the same
buf to fill them.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
It access hardware, hence why the simple igt_only_list_subtests()
check from igt_fork/stop_signal_helper() isn't enough.
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
|
|
Set bit 21 to enable qword writes for Broadwell.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Since we do not use the allow-48b GTT per-object flag, even on
Broadwell+ we will be constrained to 4GiB of usage GTT.
Also only do a single pass for BAT as suggested by Marius Vlad.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
Since we want to focus on the issue of running with a full-gtt, and part
of that is in handling the eviction, do a warm-up pass before we start
the clock that allocates the objects and fills the gtt.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
|
This is an attempt to emulate the stressful nature of gem_cs_prefetch
without being as slow i.e. without trying to detect the GPU prefetch
issues and just emphasive the basic correctness in handling enough
batches to fill the GTT similar to gem_ringfill aims to fill a ring.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
|
