From: Dave Gordon <david.s.gordon@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Rename __force_wake_get to __force_wake_auto
Date: Thu, 24 Mar 2016 15:12:02 +0000 [thread overview]
Message-ID: <56F403C2.8030509@intel.com> (raw)
In-Reply-To: <1458829907-26596-1-git-send-email-chris@chris-wilson.co.uk>
On 24/03/16 14:31, Chris Wilson wrote:
> __force_wake_get() only acquire a temporary wakeref on forcewake that is
> automatically releases when a timer expires. When reading the code
> again, I confused __intel_uncore_forcewake_get for __force_wake_get and
> to my shame thought I found a bug in an unbalanced wake_count handling.
>
> I claim that if the function had been called __force_wake_auto instead I
> would not have embarrassed myself.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_uncore.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
But how does this fit with arming the timer from the put() elsewhere?
For consistency, should we not also arm it during the put() stage of
these combined get-access-put functions? In other words, put it into the
GEN6_{READ,WRITE}_FOOTER macros? And could they not be structured to use
the same underlying set of functions, i.e. get -> inc ref, write
register if previously zero, put->if ref == 1, arm timer, else dec ref?
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-24 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 14:31 [PATCH] drm/i915: Rename __force_wake_get to __force_wake_auto Chris Wilson
2016-03-24 15:12 ` Dave Gordon [this message]
2016-03-24 15:28 ` Chris Wilson
2016-03-24 15:19 ` Tvrtko Ursulin
2016-03-24 16:02 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-03-30 10:19 ` Mika Kuoppala
2016-03-31 11:13 ` ✗ Fi.CI.BAT: failure " Patchwork
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=56F403C2.8030509@intel.com \
--to=david.s.gordon@intel.com \
--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.