public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH 3/6] drm/i915: Mark all default contexts as uninitialised after context loss
Date: Wed, 25 May 2016 15:43:46 +0300	[thread overview]
Message-ID: <1464180226.4875.23.camel@linux.intel.com> (raw)
In-Reply-To: <1464176933-31067-4-git-send-email-chris@chris-wilson.co.uk>

On ke, 2016-05-25 at 12:48 +0100, Chris Wilson wrote:
> When the GPU is reset or state lost through suspend, every default
> legacy context needs to reload their state - both the golden render
> state and the L3 mapping. Only context images explicitly saved to memory
> (i.e. all execlists and non-default legacy contexts) will retain their
> state across the reset.
> 

Should not hurt at least.

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>  drivers/gpu/drm/i915/i915_gem_context.c | 17 +++++++++++++++--
>  1 file changed, 15 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index 3e3acd054f05..62de72a947e5 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -470,7 +470,21 @@ void i915_gem_context_lost(struct drm_i915_private *dev_priv)
>  		}
>  	}
>  
> -	/* Force the GPU state to be restore on enabling */
> +	/* Force the GPU state to be restored on enabling */
> +	if (!i915.enable_execlists) {
> +		struct i915_gem_context *ctx;
> +
> +		list_for_each_entry(ctx, &dev_priv->context_list, link) {
> +			if (!i915_gem_context_is_default(ctx))
> +				continue;
> +
> +			for_each_engine(engine, dev_priv)
> +				ctx->engine[engine->id].initialised = false;
> +
> +			ctx->remap_slice = ALL_L3_SLICES(dev_priv);
> +		}
> +	}
> +
>  	for_each_engine(engine, dev_priv) {
>  		struct intel_context *ce =
>  			&dev_priv->kernel_context->engine[engine->id];
> @@ -478,7 +492,6 @@ void i915_gem_context_lost(struct drm_i915_private *dev_priv)
>  		ce->initialised =
>  			!i915.enable_execlists || engine->init_context == NULL;
>  	}
> -	dev_priv->kernel_context->remap_slice = ALL_L3_SLICES(dev_priv);
>  }
>  
>  void i915_gem_context_fini(struct drm_device *dev)
-- 
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

  reply	other threads:[~2016-05-25 12:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 11:48 Bug 95634, avoid fresh work on shutdown Chris Wilson
2016-05-25 11:48 ` [PATCH 1/6] drm/i915: Skip idling an idle engine Chris Wilson
2016-05-25 11:48 ` [PATCH 2/6] drm/i915: Treat kernel context as initialised Chris Wilson
2016-05-25 12:38   ` Joonas Lahtinen
2016-05-25 12:58     ` Chris Wilson
2016-05-25 12:42   ` Chris Wilson
2016-05-25 14:16   ` Mika Kuoppala
2016-05-25 14:38     ` Chris Wilson
2016-05-25 14:58     ` [PATCH] drm/i915: Defer enabling rc6 til after we submit the first batch/context Chris Wilson
2016-05-25 15:33       ` Chris Wilson
2016-05-25 17:07       ` Chris Wilson
2016-05-25 11:48 ` [PATCH 3/6] drm/i915: Mark all default contexts as uninitialised after context loss Chris Wilson
2016-05-25 12:43   ` Joonas Lahtinen [this message]
2016-05-25 11:48 ` [PATCH 4/6] drm/i915: No need to wait for idle on L3 remap Chris Wilson
2016-05-25 14:27   ` Mika Kuoppala
2016-05-25 11:48 ` [PATCH 5/6] drm/i915: Split idling from forcing context switch Chris Wilson
2016-05-25 12:57   ` Joonas Lahtinen
2016-05-25 13:12     ` Chris Wilson
2016-05-25 11:48 ` [PATCH 6/6] drm/i915: Only switch to default context when evicting from GGTT Chris Wilson
2016-05-25 12:09 ` ✗ Ro.CI.BAT: failure for series starting with [1/6] drm/i915: Skip idling an idle engine Patchwork
2016-05-25 14:04 ` [PATCH v2 1/6] " Chris Wilson
2016-05-25 14:04   ` [PATCH v2 2/6] drm/i915: Move legacy kernel context pinning to intel_ringbuffer.c Chris Wilson
2016-05-26 10:22     ` Joonas Lahtinen
2016-05-26 10:29       ` Chris Wilson
2016-05-26 11:18       ` [PATCH] " Chris Wilson
2016-05-26 11:30         ` Joonas Lahtinen
2016-05-26 12:52         ` Mika Kuoppala
2016-05-25 14:04   ` [PATCH v2 3/6] drm/i915: Treat kernel context as initialised Chris Wilson
2016-05-25 14:04   ` [PATCH v2 4/6] drm/i915: Mark all default contexts as uninitialised after context loss Chris Wilson
2016-05-25 14:04   ` [PATCH v2 5/6] drm/i915: No need to wait for idle on L3 remap Chris Wilson
2016-05-25 14:04   ` [PATCH v2 6/6] drm/i915: Split idling from forcing context switch Chris Wilson
2016-05-25 14:59 ` ✗ Ro.CI.BAT: failure for series starting with [1/6] drm/i915: Skip idling an idle engine (rev6) Patchwork
2016-05-25 15:00 ` ✗ Ro.CI.BAT: failure for series starting with [1/6] drm/i915: Skip idling an idle engine (rev7) Patchwork
2016-05-26  5:00 ` ✗ Ro.CI.BAT: failure for series starting with [1/6] drm/i915: Skip idling an idle engine (rev8) Patchwork
2016-05-26 11:20 ` ✗ Ro.CI.BAT: failure for series starting with [1/6] drm/i915: Skip idling an idle engine (rev9) 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=1464180226.4875.23.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@intel.com \
    /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