[Bug 102199] Kabylake has poor performance, doesn't upclock during activity quickly with single display configurations
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Aug 22 16:13:26 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=102199
--- Comment #23 from Chris Wilson <chris at chris-wilson.co.uk> ---
Applied commit 74d290f845d0736bf6b9dd22cd28dd87b270c65f
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Thu Aug 17 13:37:06 2017 +0100
drm/i915: Boost GPU clocks if we miss the pageflip's vblank
If we miss the current vblank because the gpu was busy, that may cause a
jitter as the frame rate temporarily drops. We try to limit the impact
of this by then boosting the GPU clock to deliver the frame as quickly
as possible. Originally done in commit 6ad790c0f5ac ("drm/i915: Boost GPU
frequency if we detect outstanding pageflips") but was never forward
ported to atomic and finally dropped in commit fd3a40242e87 ("drm/i915:
Rip out legacy page_flip completion/irq handling").
One of the most typical use-cases for this is a mostly idle desktop.
Rendering one frame of the desktop's frontbuffer can easily be
accomplished by the GPU running at low frequency, but often exceeds
the time budget of the desktop compositor. The result is that animations
such as opening the menu, doing a fullscreen switch, or even just trying
to move a window around are slow and jerky. We need to respond within a
frame to give the best impression of a smooth UX, as a compromise we
instead respond if that first frame misses its goal. The result should
be a near-imperceivable initial delay and a smooth animation even
starting from idle. The cost, as ever, is that we spend more power than
is strictly necessary as we overestimate the required GPU frequency and
then try to ramp down.
This of course is reactionary, too little, too late; nevertheless it is
surprisingly effective.
It should provide us with a good safety net. Ideally we still want to tell in
advance when we need to boost the clocks to hit a user deadline.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170822/437790c5/attachment.html>
More information about the intel-gfx-bugs
mailing list