From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: don't rewrite the GTT on resume
Date: Mon, 15 Oct 2012 10:42:03 +0100 [thread overview]
Message-ID: <453bf0$631iug@azsmga001.ch.intel.com> (raw)
In-Reply-To: <b94cdc$6v3soq@fmsmga001.fm.intel.com>
On Mon, 15 Oct 2012 09:37:00 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Sun, 14 Oct 2012 19:10:38 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > The BIOS shouldn't be touching this memory across suspend/resume, so
> > just leave it alone. This saves us ~50ms on resume on my T420.
> >
> > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> > ---
> > drivers/gpu/drm/i915/i915_drv.c | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> > index 824e3c8..95e2b8b 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.c
> > +++ b/drivers/gpu/drm/i915/i915_drv.c
> > @@ -119,6 +119,10 @@ module_param_named(i915_enable_ppgtt, i915_enable_ppgtt, int, 0600);
> > MODULE_PARM_DESC(i915_enable_ppgtt,
> > "Enable PPGTT (default: true)");
> >
> > +int i915_needs_gtt_restore __read_mostly = 0;
> > +module_param_named(gtt_restore, i915_needs_gtt_restore, int, 0600);
> > +MODULE_PARM_DESC(gtt_restore, "Rewrite GTT on resume (default: false)");
>
> Wrong way around. This code exists purely because KMS resume was broken
> on a number of machines without reinitialising the GTT, ergo this is a
> regression.
Looking into the history, at the time we wrote the GTT reinit, I believe
we did not have a GFX_FLUSH_CNTL in the resume path. Now we do, so I'd
be more inclined to believe that we have fixed a bug in the meantime. If
so, we only need to be extra careful for gen2.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-10-15 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 2:10 [PATCH 1/3] drm/i915: don't block resume on fb console resume Jesse Barnes
2012-10-15 2:10 ` [PATCH 2/3] drm/i915: put ring frequency and turbo setup into a work queue Jesse Barnes
2012-10-15 7:46 ` Daniel Vetter
2012-10-15 2:10 ` [PATCH 3/3] drm/i915: don't rewrite the GTT on resume Jesse Barnes
2012-10-15 7:41 ` Daniel Vetter
2012-10-15 15:49 ` Jesse Barnes
2012-10-15 8:37 ` Chris Wilson
2012-10-15 9:42 ` Chris Wilson [this message]
2012-10-15 15:49 ` Jesse Barnes
2012-10-15 2:32 ` [PATCH 1/3] drm/i915: don't block resume on fb console resume Dave Airlie
2012-10-15 4:49 ` Jesse Barnes
2012-10-15 7:30 ` Dave Airlie
2012-10-15 9:26 ` Chris Wilson
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='453bf0$631iug@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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