intel-gfx.lists.freedesktop.org archive mirror
 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
Subject: Re: [PATCH v3 26/33] drm/i915: Treat kernel context as initialised
Date: Tue, 07 Jun 2016 12:23:34 +0300	[thread overview]
Message-ID: <1465291414.5626.4.camel@linux.intel.com> (raw)
In-Reply-To: <1464964636-3877-27-git-send-email-chris@chris-wilson.co.uk>

On pe, 2016-06-03 at 15:37 +0100, Chris Wilson wrote:
> The kernel context exists simply as a placeholder and should never be
> executed with a render context. It does not need the golden render
> state, as that will always be applied to a user context. By skipping the
> initialisation we can avoid issues in attempting to program the golden
> render context when trying to make the hardware idle.
> 
> v2: Rebase
> 
> Testcase: igt/drm_module_reload_basic #byt
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=95634
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>  drivers/gpu/drm/i915/i915_gem_context.c | 14 +++++++++-----
>  drivers/gpu/drm/i915/intel_ringbuffer.c | 10 ++++++++++
>  2 files changed, 19 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index c620fe6c9d96..d0076838e788 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -434,13 +434,17 @@ void i915_gem_context_lost(struct drm_i915_private *dev_priv)
>  			i915_gem_context_unpin(engine->last_context, engine);
>  			engine->last_context = NULL;
>  		}
> -
> -		/* Force the GPU state to be reinitialised on enabling */
> -		dev_priv->kernel_context->engine[engine->id].initialised =
> -			engine->init_context == NULL;
>  	}
>  
> -	/* Force the GPU state to be reinitialised on enabling */
> +	/* Force the GPU state to be restored on enabling */
> +	if (!i915.enable_execlists) {
> +		for_each_engine(engine, dev_priv) {
> +			struct intel_context *ce =

Here I would name it as "kce", to make explicit it's about kernel
context engines.

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

> +				&dev_priv->kernel_context->engine[engine->id];
> +
> +			ce->initialised = true;
> +		}
> +	}
>  	dev_priv->kernel_context->remap_slice = ALL_L3_SLICES(dev_priv);
>  }
>  
> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> index 92bb376e5039..1a389d0dcdd2 100644
> --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> @@ -2257,6 +2257,16 @@ static int intel_ring_context_pin(struct i915_gem_context *ctx,
>  			goto error;
>  	}
>  
> +	/* The kernel context is only used as a placeholder for flushing the
> +	 * active context. It is never used for submitting user rendering and
> +	 * as such never requires the golden render context, and so we can skip
> +	 * emitting it when we switch to the kernel context. This is required
> +	 * as during eviction, we cannot allocate and pin the renderstate in
> +	 * order to initialise the context.
> +	 */
> +	if (ctx == ctx->i915->kernel_context)
> +		ce->initialised = true;
> +
>  	i915_gem_context_reference(ctx);
>  	return 0;
>  
-- 
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-06-07  9:23 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 14:36 BAT regression bug 95634, take 3 Chris Wilson
2016-06-03 14:36 ` [PATCH v3 01/33] drm: Export drm_dev_init() for subclassing Chris Wilson
2016-06-03 14:36 ` [PATCH v3 02/33] drm: Add a callback from connector registering Chris Wilson
2016-06-03 14:36 ` [PATCH v3 03/33] drm: Make drm_connector_register() safe against multiple calls Chris Wilson
2016-06-03 14:36 ` [PATCH v3 04/33] drm: Automatically unregister the connector during cleanup Chris Wilson
2016-06-03 14:36 ` [PATCH v3 05/33] drm: Pass the drm_dp_aux->hw_mutex to i2c for its locking Chris Wilson
2016-06-03 15:11   ` Ville Syrjälä
2016-06-03 14:36 ` [PATCH v3 06/33] drm: Minimally initialise drm_dp_aux Chris Wilson
2016-06-03 14:59   ` Ville Syrjälä
2016-06-09 20:57     ` Chris Wilson
2016-06-10 10:26       ` Ville Syrjälä
2016-06-10 10:50         ` Chris Wilson
2016-06-03 14:36 ` [PATCH v3 07/33] drm/i915: Perform async fbdev initialisation much later Chris Wilson
2016-06-03 14:36 ` [PATCH v3 08/33] drm/i915: Make panel/backlight safe to setup/cleanup multiple times Chris Wilson
2016-06-03 14:36 ` [PATCH v3 09/33] drm/i915: Move panel's pipe from backlight setup to init Chris Wilson
2016-06-03 15:04   ` Ville Syrjälä
2016-06-03 15:22     ` Chris Wilson
2016-06-03 14:36 ` [PATCH v3 10/33] drm/i915: Move intel_connector->unregister to connector->early_unregister Chris Wilson
2016-06-03 14:36 ` [PATCH v3 11/33] drm/i915: Move backlight unregistration to connector unregistration Chris Wilson
2016-06-03 14:36 ` [PATCH v3 12/33] drm/i915: Move registration actions to connector->late_register Chris Wilson
2016-06-03 14:36 ` [PATCH v3 13/33] drm/i915/dp: Free the drm_dp_aux along with the encoder Chris Wilson
2016-06-03 14:36 ` [PATCH v3 14/33] drm/i915: Move backlight setup to connector registration Chris Wilson
2016-06-03 14:36 ` [PATCH v3 15/33] drm/i915: Move backlight registration " Chris Wilson
2016-06-03 14:36 ` [PATCH v3 16/33] drm/i915: Move connector registration to driver registration Chris Wilson
2016-06-03 14:37 ` [PATCH v3 17/33] drm/i915: Register debugfs interface last Chris Wilson
2016-06-03 14:37 ` [PATCH v3 18/33] drm/i915: Demidlayer driver loading Chris Wilson
2016-06-03 14:37 ` [PATCH v3 19/33] drm/i915: Demidlayer driver unloading Chris Wilson
2016-06-03 14:37 ` [PATCH v3 20/33] drm/i915: Start exploiting drm_device subclassing Chris Wilson
2016-06-03 14:37 ` [PATCH v3 21/33] drm/i915: Merge i915_dma.c into i915_drv.c Chris Wilson
2016-06-03 14:37 ` [PATCH v3 22/33] drm/i915: Split out the PCI driver interface to i915_pci.c Chris Wilson
2016-06-03 14:37 ` [PATCH v3 23/33] drm/i915: Move module init/exit " Chris Wilson
2016-06-08  8:57   ` Joonas Lahtinen
2016-06-03 14:37 ` [PATCH v3 24/33] drm/i915: Skip idling an idle engine Chris Wilson
2016-06-03 14:37 ` [PATCH v3 25/33] drm/i915: Move legacy kernel context pinning to intel_ringbuffer.c Chris Wilson
2016-06-03 14:37 ` [PATCH v3 26/33] drm/i915: Treat kernel context as initialised Chris Wilson
2016-06-07  9:23   ` Joonas Lahtinen [this message]
2016-06-03 14:37 ` [PATCH v3 27/33] drm/i915: Mark all default contexts as uninitialised after context loss Chris Wilson
2016-06-03 14:37 ` [PATCH v3 28/33] drm/i915: No need to wait for idle on L3 remap Chris Wilson
2016-06-03 14:37 ` [PATCH v3 29/33] drm/i915: Split idling from forcing context switch Chris Wilson
2016-06-08  9:02   ` Joonas Lahtinen
2016-06-08 10:56     ` Chris Wilson
2016-06-03 14:37 ` [PATCH v3 30/33] drm/i915: Only switch to default context when evicting from GGTT Chris Wilson
2016-06-03 14:37 ` [PATCH v3 31/33] drm/i915: Preserve current RPS frequency Chris Wilson
2016-06-03 14:37 ` [PATCH v3 32/33] drm/i915: Remove superfluous powersave work flushing Chris Wilson
2016-06-03 14:37 ` [PATCH v3 33/33] drm/i915: Defer enabling rc6 til after we submit the first batch/context Chris Wilson
2016-06-03 15:17 ` ✗ Ro.CI.BAT: warning for series starting with [v3,01/33] drm: Export drm_dev_init() for subclassing 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=1465291414.5626.4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).