From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99955] [r600g] GPU load always displayed at 100% with GALLIUM_HUD=GPU-load
Date: Sat, 25 Feb 2017 00:38:05 +0000 [thread overview]
Message-ID: <bug-99955-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99955
Bug ID: 99955
Summary: [r600g] GPU load always displayed at 100% with
GALLIUM_HUD=GPU-load
Product: Mesa
Version: git
Hardware: All
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: megwattt@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Hello,
The GPU-load graph from GALLIUM_HUD will always be at 100%, no matter what
application is launched (even glxgears with vblank_mode=3). I tested that on my
Radeon HD 5770.
This regression is caused by commit b8f3b00742eab6ee1868407b876f69195a51f3b6 :
gallium/radeon: include SDMA in the GPU load query.
It doesn't seems to affect radeonsi, as the GPU-load results on a TOPAZ XT chip
are more reasonable (~5% with the same test).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2469 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 reply other threads:[~2017-02-25 0:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 0:38 bugzilla-daemon [this message]
2017-03-05 17:46 ` [Bug 99955] [r600g] GPU load always displayed at 100% with GALLIUM_HUD=GPU-load bugzilla-daemon
2017-03-06 15:20 ` bugzilla-daemon
2017-03-06 15:53 ` bugzilla-daemon
2017-03-31 7:42 ` bugzilla-daemon
2017-03-31 14:36 ` bugzilla-daemon
2017-03-31 15:01 ` bugzilla-daemon
2019-09-18 19:22 ` bugzilla-daemon
2019-09-19 13:46 ` 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-99955-502@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).