From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100742] dpm auto doesn't clock the GPU high enough for SteamVR apps
Date: Thu, 20 Apr 2017 21:31:22 +0000 [thread overview]
Message-ID: <bug-100742-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1831 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100742
Bug ID: 100742
Summary: dpm auto doesn't clock the GPU high enough for SteamVR
apps
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: haagch@frickel.club
RX 480, Ryzen 1600X, tested on linux 4.10 and linux drm-next-4.12-wip, latest
upstream linux-firmware git. Same behavior on both kernels.
I recorded this video, showing umr top, sclk and mclk, while running the simple
"Atlas Demo Scene" in the Destinations SteamVR app:
https://www.youtube.com/watch?v=U_mceDSBF7o
With the "auto" setting the GPU power level is not set high enough for SteamVR
to render at the Vive's native 90 fps, so reprojection (interpolation to 90
fps) needs to kick in constantly.
Speculation time:
The SteamVR frametime graph shows the purple GPU load from the application
("Destinations") completely below the 11 ms which the application is probably
is probably targeting, so dpm has clocked the GPU fast enough for the
application to run at 90 fps. But then the application submits frames to the
SteamVR compositor which also takes some GPU time and pushes the "total" GPU
time taken to render one frame in the app and then display it in the compositor
over the target 11 ms time.
Is this correct? Does dpm somehow analyze a per process GPU load? At least in
this case the GPU needs to clock fast enough to allow the application + the
SteamVR compositor to both render in under 11 ms per frame.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3215 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-04-20 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 21:31 bugzilla-daemon [this message]
2017-07-04 21:25 ` [Bug 100742] dpm auto doesn't clock the GPU high enough for SteamVR apps bugzilla-daemon
2017-07-11 21:33 ` bugzilla-daemon
2017-07-11 22:43 ` bugzilla-daemon
2018-09-09 10:12 ` bugzilla-daemon
2019-11-19 8:15 ` 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-100742-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.