Bug 107376 - Raven: `flush_delayed_work()` takes 500 ms
Summary: Raven: `flush_delayed_work()` takes 500 ms
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 107278
  Show dependency treegraph
 
Reported: 2018-07-25 13:51 UTC by Paul Menzel
Modified: 2019-11-20 07:49 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
HTML output of `sudo ./sleepgraph.py -config config/suspend-callgraph.cfg` (devicelist: amdgpu, maxdepth: 12) (1.64 MB, text/html)
2018-07-25 13:51 UTC, Paul Menzel
no flags Details

Description Paul Menzel 2018-07-25 13:51:58 UTC
Created attachment 140811 [details]
HTML output of `sudo ./sleepgraph.py -config config/suspend-callgraph.cfg` (devicelist: amdgpu, maxdepth: 12)

Created attachment 140810 [details]
HTML output of `sudo ./sleepgraph.py -config config/suspend-callgraph.cfg` (devicelist: amdgpu, maxdepth: 12)

Profiling the suspend and resume time [1] on a MSI B350M MORTAR (MS-7A37) with AMD Ryzen 3 2200G with Radeon Vega Graphics with Linux 4.18-rc6+ and amd-staging-drm-next [2], `pci_pm_suspend()` takes over one second, which is too long [3], cf. bug 107278 [3].

This is spent in `amdgpu_device_ip_resume_phase2()`, where 505 ms are spent in `flush_delayed_work()`.

•   flush_delayed_work (505.026 ms @ 98.640854)
    […]
    •   flush_work (505.017 ms @ 98.640863)
        […]
        •   wait_for_completion (504.985 ms @ 98.640894)
            […]
            •    schedule_timeout (504.963 ms @ 98.640914)
                 […]
                 •   schedule (504.963 ms @ 98.640914)

[1]: https://01.org/suspendresume
[2]: https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
[3]: https://bugs.freedesktop.org/show_bug.cgi?id=107278
Comment 1 Martin Peres 2019-11-20 07:49:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/464.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.