Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: optionally check GTT checksum across suspend/resume
Date: Wed, 12 Sep 2012 23:02:43 -0700	[thread overview]
Message-ID: <20120912230243.1b8e6679@bwidawsk.net> (raw)
In-Reply-To: <1347481630-2986-1-git-send-email-jbarnes@virtuousgeek.org>

On Wed, 12 Sep 2012 13:27:10 -0700
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> This adds a module parameter, gtt_suspend_verify, that will enable a
> simple GTT checksum across suspend and resume.
> 
> We currently spend a good amount of time (>20ms) clearing all the GTT
> PTEs at resume time, even though this may not be necessary on some
> machines.  This debug feature is intended to help determine whether
> newer machines don't need the unconditional GTT clear on resume.
> 
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>


It's a cool idea, but I'd vote against adding a module parameter to
verify it. Daniel's trees should be well enough tested that
you could just disable it on IVB+ or whatever and let it go through QA
and developer testing. Aside from that, a debugfs flag to toggle it
would probably be a little better.

Also, as a bikeshed you could probably get a much better detection with
a CRC or something similar.

I dunno, just a thought,
-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2012-09-13  6:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 20:27 [PATCH] drm/i915: optionally check GTT checksum across suspend/resume Jesse Barnes
2012-09-13  6:02 ` Ben Widawsky [this message]
2012-09-13 14:48   ` Keith Packard

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=20120912230243.1b8e6679@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --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