dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100941] Improve time to suspend on
Date: Fri, 05 May 2017 07:04:32 +0000	[thread overview]
Message-ID: <bug-100941-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2877 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100941

            Bug ID: 100941
           Summary: Improve time to suspend on
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: paulepanter@users.sourceforge.net

Created attachment 131223
  --> https://bugs.freedesktop.org/attachment.cgi?id=131223&action=edit
TML page generated by pm-graph (`sudo ./analyze_suspend.py -config
config/suspend-callgraph.cfg`)

The ASRock E350M1 has a Radeon HD 6310.

```
$ sudo lspci -s 0:01.0 -nn -v
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller])
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD
6310] [1002:9802]
        Flags: bus master, fast devsel, latency 0, IRQ 28
        Memory at e0000000 (32-bit, prefetchable) [size=256M]
        I/O ports at 2000 [size=256]
        Memory at f0100000 (32-bit, non-prefetchable) [size=256K]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
        Kernel driver in use: radeon
        Kernel modules: radeon
```

With Debian Sid/unstable with Linux 4.9.25 suspend and resume times are
benchmarked with pm-graph [1], and the command below.

```
sudo ./analyze_suspend.py -config config/suspend-callgraph.cfg
```

It turns out that with 258 ms the radeon module takes the majority of the time
during suspend.

In that cycle one `radeon_bo_evict_vram` call takes the longest with 198 ms.

```
[…]
  459.186778 |   0)  kworker-1495  |   0.974 us    |         
radeon_fence_wait_empty [radeon]();
  459.186780 |   0)  kworker-1495  |   0.440 us    |         
radeon_fence_wait_empty [radeon]();
  459.186783 |   0)  kworker-1495  |   0.501 us    |         
radeon_fence_wait_empty [radeon]();
  459.186785 |   0)  kworker-1495  |   5.424 us    |         
radeon_save_bios_scratch_regs [radeon]();
  459.186793 |   0)  kworker-1495  |   7625.511 us |          evergreen_suspend
[radeon]();
  459.194422 |   0)  kworker-1495  |   10.158 us   |         
evergreen_hpd_fini [radeon]();
  459.194434 |   0)  kworker-1495  |   198203.3 us |         
radeon_bo_evict_vram [radeon]();
[…]
```

Please see the attached files for more details.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4443 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

             reply	other threads:[~2017-05-05  7:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  7:04 bugzilla-daemon [this message]
2017-05-05  7:05 ` [Bug 100941] Improve time to suspend on bugzilla-daemon
2017-05-05  7:06 ` bugzilla-daemon
2017-05-06 18:50 ` [Bug 100941] Improve time to suspend on Radeon HD 6310 bugzilla-daemon
2017-05-06 18:57 ` bugzilla-daemon
2017-05-06 19:44 ` bugzilla-daemon
2017-05-07  8:55 ` bugzilla-daemon
2018-07-31 16:41 ` bugzilla-daemon
2019-11-19  9:28 ` 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-100941-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