From: Keith Packard <keithp@keithp.com>
To: Ben Widawsky <ben@bwidawsk.net>, Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: force wake reference counting (another try)
Date: Tue, 12 Apr 2011 09:56:03 -0700 [thread overview]
Message-ID: <yunr597pfx8.fsf@aiko.keithp.com> (raw)
In-Reply-To: <20110412163022.GA12791@snipes.kumite>
[-- Attachment #1.1: Type: text/plain, Size: 513 bytes --]
On Tue, 12 Apr 2011 09:30:22 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> I am going to spend at least a day tracking down, and hopefully fixing
> warnings if you agree with my next statement that it is in fact a
> problem. My hope is there aren't too many cases.
I can't see how we can survive without using exactly one lock covering
the wake locks on SNB. Has someone tried sticking a simple spinlock
around the whole sequence (force_wake_get, op, force_wake_put)?
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-04-12 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 1:01 force wake reference counting (another try) Ben Widawsky
2011-04-12 1:01 ` [PATCH 1/4] drm/i915: proper use of forcewake Ben Widawsky
2011-04-12 1:01 ` [PATCH 2/4] drm/i915: refcounts for forcewake Ben Widawsky
2011-04-12 1:01 ` [PATCH 3/4] drm/i915: userspace interface to the forcewake refcount Ben Widawsky
2011-04-12 1:01 ` [PATCH 4/4] drm/i915: fewer warning patch (temporary) Ben Widawsky
2011-04-12 8:02 ` force wake reference counting (another try) Chris Wilson
2011-04-12 16:30 ` Ben Widawsky
2011-04-12 16:56 ` Keith Packard [this message]
2011-04-12 17:21 ` Chris Wilson
2011-04-12 17:41 ` Keith Packard
2011-04-13 1:31 ` Ben Widawsky
2011-04-13 5:31 ` Keith Packard
2011-04-13 5:52 ` Chris Wilson
2011-04-13 6:35 ` Ben Widawsky
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=yunr597pfx8.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=ben@bwidawsk.net \
--cc=chris@chris-wilson.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.