<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@drv_selftest@live_gtt - incomplete"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107127#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@drv_selftest@live_gtt - incomplete"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107127">bug 107127</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>At the beginning of the test on these platforms we try to create a fully
populated 4G ppgtt, and then the test goes on to try and fill all of memory to
see how close to a 48b gtt we can create (although it gives up on a timeout).
This test is prone to oom and watchdog. I think it makes some sense to prune
the worst offenders for fast-feedback (in the same way as we limit individual
tests to run within a timeout rather than try and exercise the whole parameter
space). Not sure on how we want to go about that though.
drv_selftest --fast-feedback
drv_selftest --quick
? Which then feed through to a i915 module parameter.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>