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 107277] Raven: pci_pm_suspend takes over 1 second
Date: Wed, 18 Jul 2018 15:37:10 +0000	[thread overview]
Message-ID: <bug-107277-502-S5P5moxZbl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107277-502@http.bugs.freedesktop.org/>


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

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

--- Comment #4 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Paul Menzel from comment #3)
> (In reply to Christian König from comment #2)
> > There isn't much you can do here:
> > > amdgpu_bo_evict_vram [amdgpu] (306.331 ms @ 74.694620)
> > 
> > This is evacuating the content of VRAM to RAM/disk to make sure we don't
> > lose screen content while suspended.
> 
> I do not understand that. The integrated graphics device uses the system RAM
> as VRAM doesn’t it? So why does it have to be evicted at all? Also, I
> believe it’s 1 GB of VRAM. That means the speed would be 3 GB/s, where it
> should be much higher with DDR4 shouldn’t it?

It's not a problem with S3 (suspend to ram), but it is for S4 (suspend to disk)
because power will be lost and the vram carve out area is not managed by the
OS.  Currently S3 and S4 share the same code paths, so they would need to be
reworked to handle S3 and S4 differently.  As for the time it takes, depending
on how much system memory is in use, some stuff may have to be swapped out to
disk to make room for all of the buffers in vram, so a lot of shuffling may
need to take place.

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

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

  parent reply	other threads:[~2018-07-18 15:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 14:47 [Bug 107277] Raven: pci_pm_suspend takes over 1 second bugzilla-daemon
2018-07-18 14:50 ` bugzilla-daemon
2018-07-18 15:05 ` bugzilla-daemon
2018-07-18 15:19 ` bugzilla-daemon
2018-07-18 15:27 ` bugzilla-daemon
2018-07-18 15:37 ` bugzilla-daemon [this message]
2018-07-18 15:44 ` bugzilla-daemon
2018-07-18 15:44 ` bugzilla-daemon
2018-07-18 17:17 ` bugzilla-daemon
2018-07-19 15:15 ` bugzilla-daemon
2018-07-19 15:46 ` bugzilla-daemon
2018-07-19 15:56 ` bugzilla-daemon
2018-07-19 16:35 ` bugzilla-daemon
2018-07-20 15:28 ` bugzilla-daemon
2018-07-20 16:30 ` bugzilla-daemon
2018-07-23  9:36 ` bugzilla-daemon
2018-07-31 16:43 ` bugzilla-daemon
2019-11-19  8:44 ` 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-107277-502-S5P5moxZbl@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