From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] drm/i915: Only do gtt cleanup in vma_unbind for the global vma
Date: Wed, 14 May 2014 19:14:13 +0300 [thread overview]
Message-ID: <20140514161413.GN18465@intel.com> (raw)
In-Reply-To: <1392383167-19948-3-git-send-email-daniel.vetter@ffwll.ch>
On Fri, Feb 14, 2014 at 02:06:07PM +0100, Daniel Vetter wrote:
> Otherwise we end up tearing down fences when e.g. the client quits
> way too early. Might or might not fix a fence pin_count BUG Ville has
> reported.
>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
For patches 1 and 3:
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 675ad96a43e1..fa00b26a9cf7 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -2731,12 +2731,14 @@ int i915_vma_unbind(struct i915_vma *vma)
> * cause memory corruption through use-after-free.
> */
>
> - i915_gem_object_finish_gtt(obj);
> + if (i915_is_ggtt(vma->vm)) {
> + i915_gem_object_finish_gtt(obj);
>
> - /* release the fence reg _after_ flushing */
> - ret = i915_gem_object_put_fence(obj);
> - if (ret)
> - return ret;
> + /* release the fence reg _after_ flushing */
> + ret = i915_gem_object_put_fence(obj);
> + if (ret)
> + return ret;
> + }
>
> trace_i915_vma_unbind(vma);
>
> --
> 1.8.5.2
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-05-14 16:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 20:49 [PATCH 1/2] drm/i915: Don't drop pinned fences Daniel Vetter
2014-01-27 20:49 ` [PATCH 2/2] drm/i915: Only do gtt cleanup in vma_unbind for the global vma Daniel Vetter
2014-01-27 21:26 ` [PATCH 1/2] drm/i915: Don't drop pinned fences Chris Wilson
2014-01-27 21:41 ` Daniel Vetter
2014-01-28 12:40 ` Ville Syrjälä
2014-02-14 13:06 ` [PATCH 1/3] " Daniel Vetter
2014-02-14 13:06 ` [PATCH 2/3] drm/i915: tune down user-triggerable dmesg noise in the cursor/overlay code Daniel Vetter
2014-02-14 17:29 ` Damien Lespiau
2014-02-14 18:02 ` Daniel Vetter
2014-02-14 13:06 ` [PATCH 3/3] drm/i915: Only do gtt cleanup in vma_unbind for the global vma Daniel Vetter
2014-02-14 13:23 ` Ville Syrjälä
2014-02-14 13:26 ` Chris Wilson
2014-05-12 17:46 ` [PATCH igt] tests/kms_fence_pin_leak: Exercise full ppgtt fence pin_count leak in the kernel ville.syrjala
2014-05-12 18:34 ` Daniel Vetter
2014-05-13 8:24 ` Ville Syrjälä
2014-05-13 8:42 ` Daniel Vetter
2014-05-13 8:56 ` [PATCH v2 " ville.syrjala
2014-05-14 16:14 ` Ville Syrjälä [this message]
2014-05-14 16:40 ` [PATCH 3/3] drm/i915: Only do gtt cleanup in vma_unbind for the global vma Daniel Vetter
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=20140514161413.GN18465@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--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