<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [Kabylake] RPS waitboost regression since v4.20" href="https://bugs.freedesktop.org/show_bug.cgi?id=109408#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [Kabylake] RPS waitboost regression since v4.20" href="https://bugs.freedesktop.org/show_bug.cgi?id=109408">bug 109408</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre><a href="https://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=prescheduler">https://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=prescheduler</a> contains commit 7b581cf26a4042e9bbb8410a31647e41cacafada Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Fri Jan 25 18:01:44 2019 +0000 drm/i915: Apply rps waitboosting for dma_fence_wait_timeout() As time goes by, usage of generic ioctls such as drm_syncobj and sync_file are on the increase bypassing i915-specific ioctls like GEM_WAIT. Currently, we only apply waitboosting to our driver ioctls as we track the file/client and account the waitboosting to them. However, since commit 7b92c1bd0540 ("drm/i915: Avoid keeping waitboost active for signaling threads"), we no longer have been applying the client ratelimiting on waitboosts and so that information has only been used for debug tracking. Push the application of waitboosting down to the common i915_request_wait, and apply it to all foreign fence waits as well. which might make a difference if the system has switched over to sync_file/syncobj interfaces in preference to the i915 ioctls.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>