From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5] drm/i915: Be more careful to drop the GT wakeref
Date: Fri, 18 Nov 2016 13:22:11 +0200 [thread overview]
Message-ID: <1479468131.3594.16.camel@linux.intel.com> (raw)
In-Reply-To: <20161115164620.17185-1-chris@chris-wilson.co.uk>
On ti, 2016-11-15 at 16:46 +0000, Chris Wilson wrote:
> @@ -218,7 +218,12 @@ static void i915_gem_request_retire(struct drm_i915_gem_request *request)
> */
> list_del(&request->ring_link);
> request->ring->last_retired_head = request->postfix;
> - request->i915->gt.active_requests--;
> + if (!--request->i915->gt.active_requests) {
BUG_ON(!request->i915->gt.active_requests) at the top?
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-11-18 11:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 14:26 [PATCH] drm/i915: Be more careful to drop the GT wakeref Chris Wilson
2016-11-15 14:31 ` Chris Wilson
2016-11-15 15:23 ` [PATCH v3] " Chris Wilson
2016-11-15 15:24 ` [PATCH v4] " Chris Wilson
2016-11-15 14:47 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-11-15 16:16 ` ✓ Fi.CI.BAT: success for drm/i915: Be more careful to drop the GT wakeref (rev4) Patchwork
2016-11-15 16:46 ` [PATCH v5] drm/i915: Be more careful to drop the GT wakeref Chris Wilson
2016-11-18 11:22 ` Joonas Lahtinen [this message]
2016-11-18 11:39 ` Chris Wilson
2016-11-18 11:50 ` Chris Wilson
2016-11-18 12:25 ` Imre Deak
2016-11-18 12:35 ` Chris Wilson
2016-11-15 17:45 ` ✗ Fi.CI.BAT: warning for drm/i915: Be more careful to drop the GT wakeref (rev5) 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=1479468131.3594.16.camel@linux.intel.com \
--to=joonas.lahtinen@linux.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.