public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Protect i915_active iterators from the shrinker
Date: Mon, 11 Feb 2019 11:13:12 +0000	[thread overview]
Message-ID: <86b7d1e0-8d6d-f9a2-a3d2-bb9014785af0@linux.intel.com> (raw)
In-Reply-To: <20190208134704.23039-1-chris@chris-wilson.co.uk>


On 08/02/2019 13:47, Chris Wilson wrote:
> If we allocate while iterating the rbtree of active nodes, we may hit
> the shrinker and so retire the i915_active reap the rbtree. Modifying
> the rbtree as we iterate is not good behaviour, so acquire the
> i915_active first to keep the tree intact whenever we allocate.
> 
> Fixes: a42375af0a30 ("drm/i915: Release the active tracker tree upon idling")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
>   drivers/gpu/drm/i915/i915_active.c | 36 +++++++++++++++++++++---------
>   1 file changed, 25 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c
> index 215b6ff8aa73..db7bb5bd5add 100644
> --- a/drivers/gpu/drm/i915/i915_active.c
> +++ b/drivers/gpu/drm/i915/i915_active.c
> @@ -163,17 +163,25 @@ int i915_active_ref(struct i915_active *ref,
>   		    struct i915_request *rq)
>   {
>   	struct i915_active_request *active;
> +	int err = 0;
> +
> +	/* Prevent reaping in case we malloc/wait while building the tree */
> +	i915_active_acquire(ref);
>   
>   	active = active_instance(ref, timeline);
> -	if (IS_ERR(active))
> -		return PTR_ERR(active);
> +	if (IS_ERR(active)) {
> +		err = PTR_ERR(active);
> +		goto out;
> +	}
>   
>   	if (!i915_active_request_isset(active))
>   		ref->count++;
>   	__i915_active_request_set(active, rq);
>   
>   	GEM_BUG_ON(!ref->count);
> -	return 0;
> +out:
> +	i915_active_release(ref);
> +	return err;
>   }
>   
>   bool i915_active_acquire(struct i915_active *ref)
> @@ -223,19 +231,25 @@ int i915_request_await_active_request(struct i915_request *rq,
>   int i915_request_await_active(struct i915_request *rq, struct i915_active *ref)
>   {
>   	struct active_node *it, *n;
> -	int ret;
> +	int err = 0;
>   
> -	ret = i915_request_await_active_request(rq, &ref->last);
> -	if (ret)
> -		return ret;
> +	/* await allocates and so we need to avoid hitting the shrinker */
> +	if (i915_active_acquire(ref))
> +		goto out; /* was idle */
> +
> +	err = i915_request_await_active_request(rq, &ref->last);
> +	if (err)
> +		goto out;
>   
>   	rbtree_postorder_for_each_entry_safe(it, n, &ref->tree, node) {
> -		ret = i915_request_await_active_request(rq, &it->base);
> -		if (ret)
> -			return ret;
> +		err = i915_request_await_active_request(rq, &it->base);
> +		if (err)
> +			goto out;
>   	}
>   
> -	return 0;
> +out:
> +	i915_active_release(ref);
> +	return err;
>   }
>   
>   #if IS_ENABLED(CONFIG_DRM_I915_DEBUG_GEM)
> 

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-02-11 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 13:47 [PATCH] drm/i915: Protect i915_active iterators from the shrinker Chris Wilson
2019-02-08 14:50 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-02-08 16:51 ` ✓ Fi.CI.IGT: " Patchwork
2019-02-11 11:13 ` Tvrtko Ursulin [this message]
2019-02-11 12:50   ` [PATCH] " Chris Wilson

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=86b7d1e0-8d6d-f9a2-a3d2-bb9014785af0@linux.intel.com \
    --to=tvrtko.ursulin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox