<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [APL] [BAT] gem_exec_nop / basic sporadically fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96606#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [APL] [BAT] gem_exec_nop / basic sporadically fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96606">bug 96606</a>
from <span class="vcard"><a class="email" href="mailto:david.s.gordon@intel.com" title="david.s.gordon@intel.com">david.s.gordon@intel.com</a>
</span></b>
<pre>IGT -basic tests really shouldn't be doing performance testing.
BASIC functionality is stuff like 'can we submit batches' and 'does this
display work', not timings of complicated and arbitrary patterns of usage.
This also doesn't belong in the gem_exec_nop test at all; it should be in a
dedicated performance/latency test instead, preferably one which explains what
it's measuring and why any particular test is considered to have failed.
As it stands, it doesn't prove *anything* about any "latency introduced by the
GuC". It could just as easily be due to the pattern of batch completion on
multiple engines leading to more contention for the struct_mutex (for example).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>