<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><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> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI][SHARDS]igt@gem_eio@in-flight-contexts-immediate|igt@gem_eio@in-flight-contexts-10ms - fail - Failed assertion: igt_seconds_elapsed(&ts) <= 10"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111925">bug 111925</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>REOPENED
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI][SHARDS]igt@gem_eio@in-flight-contexts-immediate|igt@gem_eio@in-flight-contexts-10ms - fail - Failed assertion: igt_seconds_elapsed(&ts) <= 10"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111925#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI][SHARDS]igt@gem_eio@in-flight-contexts-immediate|igt@gem_eio@in-flight-contexts-10ms - fail - Failed assertion: igt_seconds_elapsed(&ts) <= 10"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111925">bug 111925</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>Next installment of this saga,
commit a64a29e775443e869e4524e5bd3a3427225810dc (upstream/master)
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Mon Nov 11 11:36:34 2019 +0000
i915/gem_eio: Flush RCU before timing our own critical sections
We cannot control how long RCU takes to find a quiescent point as that
depends upon the background load and so may take an arbitrary time.
Instead, let's try to avoid that impacting our measurements by inserting
an rcu_barrier() before our critical timing sections and hope that hides
the issue, letting us always perform a fast reset. Fwiw, we do the
expedited RCU synchronize, but that is not always enough.
Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Acked-by: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>>
Let's be brave and like all the other times assume that this fixes it for real.</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 the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>