From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97260] [bisected] R9 290 low performance in Linux 4.7
Date: Tue, 16 Aug 2016 03:52:54 +0000 [thread overview]
Message-ID: <bug-97260-502-E5ApMmAG7w@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97260-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1141 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97260
--- Comment #18 from Michel Dänzer <michel@daenzer.net> ---
Created attachment 125808
--> https://bugs.freedesktop.org/attachment.cgi?id=125808&action=edit
radeon: Add some page flip debugging output
Well, that's a surprising result of the bisection.
I can imagine two possible causes, or possibly some combination thereof:
* The processing of asynchronous flips or the corresponding completion
interrupts
is delayed for some reason
* Using flips instead of blits for buffer swaps lowers the load on the GPU 3D
engine, so the SMU doesn't switch to higher clocks
The attached debugging patch should give us more information about the former.
With it applied, run the following while an affected application is running in
fullscreen:
sudo sh -c 'echo 2 >/sys/module/drm/parameters/debug'; sleep 1; sudo sh -c
'echo 0 >/sys/module/drm/parameters/debug'
Then attach the resulting dmesg output.
BTW, does the problem still happen with Alex's current drm-next-4.9-wip branch?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2187 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-16 3:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 13:45 [Bug 97260] R9 290 low performance in Linux 4.7 bugzilla-daemon
2016-08-09 13:48 ` bugzilla-daemon
2016-08-10 18:45 ` bugzilla-daemon
2016-08-10 19:17 ` bugzilla-daemon
2016-08-10 19:40 ` bugzilla-daemon
2016-08-10 19:43 ` bugzilla-daemon
2016-08-10 19:51 ` bugzilla-daemon
2016-08-10 20:25 ` bugzilla-daemon
2016-08-10 20:52 ` bugzilla-daemon
2016-08-10 21:00 ` bugzilla-daemon
2016-08-11 17:07 ` bugzilla-daemon
2016-08-11 19:35 ` bugzilla-daemon
2016-08-12 19:58 ` [Bug 97260] [bisected] " bugzilla-daemon
2016-08-12 19:58 ` bugzilla-daemon
2016-08-13 18:49 ` bugzilla-daemon
2016-08-15 17:57 ` bugzilla-daemon
2016-08-15 18:12 ` bugzilla-daemon
2016-08-15 20:02 ` bugzilla-daemon
2016-08-16 3:52 ` bugzilla-daemon [this message]
2016-08-16 6:15 ` bugzilla-daemon
2016-08-16 15:49 ` bugzilla-daemon
2016-08-17 8:05 ` bugzilla-daemon
2016-08-17 16:31 ` bugzilla-daemon
2016-08-18 1:02 ` bugzilla-daemon
2016-08-18 1:03 ` bugzilla-daemon
2016-08-19 6:22 ` 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-97260-502-E5ApMmAG7w@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