From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111305] `ttm_bo_handle_move_mem` sometimes takes more than 50 ms
Date: Tue, 06 Aug 2019 10:15:16 +0000 [thread overview]
Message-ID: <bug-111305-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2109 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111305
Bug ID: 111305
Summary: `ttm_bo_handle_move_mem` sometimes takes more than 50
ms
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: pmenzel+bugs.freedesktop.org@molgen.mpg.de
Created attachment 144954
--> https://bugs.freedesktop.org/attachment.cgi?id=144954&action=edit
Screenshot from callgraph excerpt
With Linux 5.3-rc3 and pm-graph’s `sleepgraph.py` [1] measuring suspend times
on the Dell OptiPlex 5040 with an external AMD graphics card, the driver needs
2.1 seconds to suspend the device, which is too long.
$ lspci -nn -s 01:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] [1002:6610] (rev 81)
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Cape
Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] [1002:aab0]
Here is the time:
0000:01:00.0 suspend (2170.017 ms @ 5037.143762 to 5039.313779)
Looking into the call graph, 1.4 s are spent in `ttm_bo_evict_mm`.
ttm_bo_evict_mm [ttm] (1438.050 ms @ 5037.601941)
As you can see in the attached screenshot, there are some
`ttm_bo_handle_move_mem` call which take several milliseconds adding up to the
long time.
- ttm_mem_evict_first [ttm] (304.860 ms @ 5037.705809)
_raw_spin_lock
mutex_trylock (0.000 ms @ 5037.705809)
+ ttm_bo_del_from_lru [ttm]
- ttm_bo_evict [ttm] (304.857 ms @ 5037.705810)
amdgpu_evict_flags [amdgpu] (0.000 ms @ 5037.705810)
ttm_bo_mem_space [ttm] (0.001 ms @ 5037.705811)
ttm_bo_handle_move_mem [ttm] (304.853 ms @ 5037.705812)
[1]: https://github.com/intel/pm-graph
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3630 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 reply other threads:[~2019-08-06 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 10:15 bugzilla-daemon [this message]
2019-08-08 17:01 ` [Bug 111305] `ttm_bo_handle_move_mem` sometimes takes more than 50 ms bugzilla-daemon
2019-08-09 0:05 ` bugzilla-daemon
2019-08-09 15:03 ` bugzilla-daemon
2019-11-19 9:38 ` 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-111305-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