From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108917] gamma adjustments cause stuttering with amdgpu.dc=1, especially problematic with RedShift etc.
Date: Tue, 19 Mar 2019 16:47:53 +0000 [thread overview]
Message-ID: <bug-108917-502-Fhd2XgxZQp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108917-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 909 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108917
--- Comment #9 from Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> ---
(In reply to tempel.julian from comment #8)
> Unfortunately, Linux 5.0.3 with
>
> drm: Block fb changes for async plane updates
> commit 25dc194b34dd5919dd07b8873ee338182e15df9d
>
> hasn't changed the situation, as far as I can tell. :(
That's the DRM level bugfix for use after free on async updates for plane
framebuffer swaps. It actually hurts performance rather than helps it.
There's a fix that allows framebuffer swaps again being developed right now
with some patches in dri-devel:
https://patchwork.freedesktop.org/series/57524/
You'd have to revert
"drm/amd/display: Skip fast cursor updates for fb changes"
as well though to actually allow this series to work.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1955 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-19 16:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 23:43 [Bug 108917] gamma adjustments cause stuttering with amdgpu.dc=1, especially problematic with RedShift etc bugzilla-daemon
2018-12-01 23:44 ` bugzilla-daemon
2018-12-03 2:59 ` bugzilla-daemon
2018-12-03 8:42 ` bugzilla-daemon
2018-12-03 9:47 ` bugzilla-daemon
2018-12-03 9:47 ` bugzilla-daemon
2018-12-03 15:33 ` bugzilla-daemon
2018-12-03 20:49 ` bugzilla-daemon
2018-12-17 14:30 ` bugzilla-daemon
2019-01-16 20:57 ` bugzilla-daemon
2019-03-19 16:44 ` bugzilla-daemon
2019-03-19 16:47 ` bugzilla-daemon [this message]
2019-03-19 18:16 ` bugzilla-daemon
2019-04-19 14:18 ` bugzilla-daemon
2019-06-27 11:02 ` bugzilla-daemon
2019-06-27 14:01 ` bugzilla-daemon
2019-06-27 19:22 ` bugzilla-daemon
2019-09-11 13:36 ` bugzilla-daemon
2019-11-19 9:06 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108917-502-Fhd2XgxZQp@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).