[Bug 111305] `ttm_bo_handle_move_mem` sometimes takes more than 50 ms

2019-11-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111305 Martin Peres changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 111305] `ttm_bo_handle_move_mem` sometimes takes more than 50 ms

2019-08-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111305 --- Comment #3 from Alex Deucher --- (In reply to Paul Menzel from comment #2) > > Just to clarify, the VRAM on the external graphics device is powered off, > correct? Correct. > > Are there any tools to analyze these delays? I guess

[Bug 111305] `ttm_bo_handle_move_mem` sometimes takes more than 50 ms

2019-08-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111305 --- Comment #2 from Paul Menzel --- (In reply to Alex Deucher from comment #1) > The contents of vram have to be moved to system memory on suspend since vram > is powered off. Depending on general memory pressure at suspend time it may > take

[Bug 111305] `ttm_bo_handle_move_mem` sometimes takes more than 50 ms

2019-08-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111305 --- Comment #1 from Alex Deucher --- The contents of vram have to be moved to system memory on suspend since vram is powered off. Depending on general memory pressure at suspend time it may take a while to get the contexts of vram into system

[Bug 111305] `ttm_bo_handle_move_mem` sometimes takes more than 50 ms

2019-08-06 Thread bugzilla-daemon
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