From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [3.0-rc3] i915: potentially stale ring data during resume
Date: Sat, 18 Jun 2011 09:12:16 -0700 [thread overview]
Message-ID: <20110618161215.GA8502@snipes.kumite> (raw)
In-Reply-To: <BANLkTi=33tNNpS-U4nU1Y-iQnLfh=Og2eQ@mail.gmail.com>
On Sat, Jun 18, 2011 at 02:48:29PM +0800, Daniel J Blueman wrote:
> Hi Eric, Chris,
>
> There are quite a lot of callers of I915_READ/WRITE which aren't
> holding the dev->struct_mutex lock across device suspend and resume
> operations, to prevent the GT going to sleep early if two callers are
> in the gen6_gt_force_wake_get->gen6_gt_force_wake_put critical region.
>
> I started cooking up a patch, but ran out of time.
Please note the only register range that matters is 0-0x40000
(don't ask how we know that).
Ben
prev parent reply other threads:[~2011-06-18 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 6:48 [3.0-rc3] i915: potentially stale ring data during resume Daniel J Blueman
2011-06-18 16:12 ` Ben Widawsky [this message]
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=20110618161215.GA8502@snipes.kumite \
--to=ben@bwidawsk.net \
--cc=daniel.blueman@gmail.com \
--cc=intel-gfx@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