mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Dave Airlie <airlied@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	"dri-devel" <dri-devel@lists.freedesktop.org>,
	linux-pm@lists.linux-foundation.org,
	Alex Deucher <alexdeucher@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ondrej Zary <linux@rainbow-software.org>
Subject: Re: [PATCH] DRM / radeon / PM: Do not evict VRAM during freeze phase of hibernation
Date: Sat, 19 Jun 2010 01:23:00 +0200	[thread overview]
Message-ID: <201006190123.00694.rjw@sisk.pl> (raw)
In-Reply-To: <1276895296.6513.3.camel@t60prh>

On Friday, June 18, 2010, Dave Airlie wrote:
> On Fri, 2010-06-18 at 22:21 +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> > 
> > I have recently noticed a 55 sec. delay during the "device freeze"
> > phase of hibernation on my test-bed HP nx6325.  Due to the 100%
> > reproducibility of it I was able to narrow it down to
> > radeon_suspend_kms() and then it turned out that the delay occured
> > somewhere in radeon_bo_evict_vram().  However, it doesn't seem really
> > necessary or even very useful to me to evict VRAM at this particular
> > point, because we're going to create an image and bring the device
> > back to the fully functional state in a little while.  Thus, I think
> > the VRAM evicition can be skipped for state.event == PM_EVENT_FREEZE,
> > which makes the delay go away.
> 
> I'm not 100% sure of the hibernate sequencing and its early in the
> morning, but we want to evict VRAM before image building so we can have
> the contents of VRAM in the image so we can restore them on resume. Does
> this just avoid evicting them a second time after we created the image?

No, it's the first time, before creating the image, but I didn't seen any
difference on resume with and without the patch, so I thought it was a good
idea. :-)

If you don't like it, though, I guess it will be necessary to find the root
cause of the delay.

Rafael

  reply	other threads:[~2010-06-18 23:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 20:21 Rafael J. Wysocki
2010-06-18 20:42 ` Rafał Miłecki
2010-06-18 23:19   ` Rafael J. Wysocki
2010-06-18 21:08 ` Dave Airlie
2010-06-18 23:23   ` Rafael J. Wysocki [this message]
2010-06-18 23:49     ` Dave Airlie
2010-06-19 12:53       ` Rafael J. Wysocki
2010-06-19 23:43         ` Rafael J. Wysocki
2010-06-21  7:57           ` Jerome Glisse
2010-06-21 20:44             ` Rafael J. Wysocki
2010-06-19 13:21       ` Rafael J. Wysocki

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=201006190123.00694.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux@rainbow-software.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

Powered by JetHome