On 5/16/2014 10:12 PM, Rodrigo Vivi wrote:
On Fri, May 16, 2014 at 3:23 AM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx
<mailto:chris@xxxxxxxxxxxxxxxxxx>> wrote:
On Thu, May 15, 2014 at 08:13:05PM -0400, Rodrigo Vivi wrote:
> The perfect solution for psr_exit is the hardware tracking the
changes and
> doing the psr exit by itself. This scenario works for HSW and BDW
with some
> environments like Gnome and Wayland.
>
> However there are many other scenarios that this isn't true.
Mainly one right
> now is KDE users on HSW and BDW with PSR on. User would miss many
screen
> updates. For instances any key typed could be seen only when
mouse cursor is
> moved. So this patch introduces the ability of trigger PSR exit
on kernel side
> on some common cases that.
You know that userspace has been waiting for a PSR flag for over a year
now so that it can use the more efficient rendering paths when it makes
sense.
yeah... this item is lingering on my to do list... but reaching a point
where I won't be able to continue postponing it ;)
What happened to the front buffer tracking?
What front buffer tracking? hehe
I'm wondering about this since I started looking to fbc and psr and
could never find a reliable way.
FBC should cover most of the scenarios except cursor planes.. When ever
cursor planes are enabled you can fall back to s/w controlled exit path.
If you can elaborate on the exact issue that you are facing with FBC and
PSR may be i can help..
Thanks,
Vijay
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
--
Rodrigo Vivi
Blog: http://blog.vivi.eng.br
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
