<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - "Avoid waitboosting" (e9af4ea2b9e7) now prevents GPU boosting"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107111#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - "Avoid waitboosting" (e9af4ea2b9e7) now prevents GPU boosting"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107111">bug 107111</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>What it is telling us is that the GPU is never utilised enough for it to
upclock by itself -- Kodi should not need more power to deliver the frames on
time, and that boosting is overkill.
One thing to confirm is which boost Kodi is depending on. So try just reverting
the intel_display chunk so that it always boost after the vblank miss.
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index 681e0710a467..0d4c61e53a6c 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -12913,7 +12913,8 @@ static int do_rps_boost(struct wait_queue_entry *_wait,
* is reasonable to assume that it will complete before the next
* vblank without our intervention, so leave RPS alone.
*/
- if (!i915_request_started(rq))
+ if (!i915_request_started(rq) ||
+ rq != i915_gem_active_peek(&rq->timeline->last_request))
gen6_rps_boost(rq, NULL);
i915_request_put(rq);
might be an interesting compromise. But what I think is that we want is more of
a nudge.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>