Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 02/18] drm/i915/ringbuffer: Brute force context restore
Date: Fri, 08 Jun 2018 16:52:13 +0300	[thread overview]
Message-ID: <874lidxu5u.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20180608125602.17693-3-chris@chris-wilson.co.uk>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> An issue encountered with switching mm on gen7 is that the GPU likes to
> hang (with the VS unit busy) when told to force restore the current
> context. We can simply workaround this by substituting the
> MI_FORCE_RESTORE flag with a round-trip through the kernel_context,
> forcing the context to be saved and restored; thereby reloading the
> PP_DIR registers and updating the modified page directory!
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Matthew Auld <matthew.william.auld@gmail.com>
> ---
>  drivers/gpu/drm/i915/intel_ringbuffer.c | 30 ++++++++++++++++++++++---
>  1 file changed, 27 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> index 65811e2fa7da..332d97bc5c27 100644
> --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> @@ -1458,6 +1458,7 @@ static inline int mi_set_context(struct i915_request *rq, u32 flags)
>  		(HAS_LEGACY_SEMAPHORES(i915) && IS_GEN7(i915)) ?
>  		INTEL_INFO(i915)->num_rings - 1 :
>  		0;
> +	bool force_restore = false;
>  	int len;
>  	u32 *cs;
>  
> @@ -1471,6 +1472,12 @@ static inline int mi_set_context(struct i915_request *rq, u32 flags)
>  	len = 4;
>  	if (IS_GEN7(i915))
>  		len += 2 + (num_rings ? 4*num_rings + 6 : 0);
> +	if (flags & MI_FORCE_RESTORE) {
> +		GEM_BUG_ON(flags & MI_RESTORE_INHIBIT);
> +		flags &= ~MI_FORCE_RESTORE;
> +		force_restore = true;
> +		len += 2;
> +	}
>  
>  	cs = intel_ring_begin(rq, len);
>  	if (IS_ERR(cs))
> @@ -1496,6 +1503,20 @@ static inline int mi_set_context(struct i915_request *rq, u32 flags)
>  	}
>  
>  	*cs++ = MI_NOOP;
> +	if (force_restore) {
> +		/*
> +		 * The HW doesn't handle being told to restore the current
> +		 * context very well. Quite often it likes goes to go off and
> +		 * sulk, especially when it is meant to be reloading PP_DIR.
> +		 * A very simple fix to force the reload is to simply switch
> +		 * away from the current context and back again.
> +		 */
> +		*cs++ = MI_SET_CONTEXT;
> +		*cs++ = i915_ggtt_offset(to_intel_context(i915->kernel_context,
> +							  engine)->state) |
> +			MI_MM_SPACE_GTT |
> +			MI_RESTORE_INHIBIT;

Why inhibit? You dont really switch to kernel but rather overwrite
current with kernel ctx.

-Mika

> +	}
>  	*cs++ = MI_SET_CONTEXT;
>  	*cs++ = i915_ggtt_offset(rq->hw_context->state) | flags;
>  	/*
> @@ -1585,11 +1606,14 @@ static int switch_context(struct i915_request *rq)
>  
>  		to_mm->pd_dirty_rings &= ~intel_engine_flag(engine);
>  		engine->legacy_active_ppgtt = to_mm;
> -		hw_flags = MI_FORCE_RESTORE;
> +
> +		if (to_ctx == from_ctx) {
> +			hw_flags = MI_FORCE_RESTORE;
> +			from_ctx = NULL;
> +		}
>  	}
>  
> -	if (rq->hw_context->state &&
> -	    (to_ctx != from_ctx || hw_flags & MI_FORCE_RESTORE)) {
> +	if (rq->hw_context->state && to_ctx != from_ctx) {
>  		GEM_BUG_ON(engine->id != RCS);
>  
>  		/*
> -- 
> 2.17.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-06-08 13:52 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08 12:55 Haswell full-ppgtt, no really Chris Wilson
2018-06-08 12:55 ` [PATCH 01/18] drm/i915: Apply batch location restrictions before pinning Chris Wilson
2018-06-08 12:55 ` [PATCH 02/18] drm/i915/ringbuffer: Brute force context restore Chris Wilson
2018-06-08 13:52   ` Mika Kuoppala [this message]
2018-06-08 14:00     ` Chris Wilson
2018-06-08 12:55 ` [PATCH 03/18] drm/i915/ringbuffer: Fix context restore upon reset Chris Wilson
2018-06-08 14:26   ` Chris Wilson
2018-06-08 17:26   ` [PATCH v2] " Chris Wilson
2018-06-08 12:55 ` [PATCH 04/18] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories Chris Wilson
2018-06-08 12:55 ` [PATCH 05/18] drm/i915/gtt: Subclass gen6_hw_ppgtt Chris Wilson
2018-06-08 12:55 ` [PATCH 06/18] drm/i915/gtt: Onionify error handling for gen6_ppgtt_create Chris Wilson
2018-06-08 12:55 ` [PATCH 07/18] drm/i915/gtt: Reorder aliasing_ppgtt fini Chris Wilson
2018-06-08 12:55 ` [PATCH 08/18] drm/i915/gtt: Make gen6 page directories evictable Chris Wilson
2018-06-08 13:10   ` [PATCH] " Chris Wilson
2018-06-08 12:55 ` [PATCH 09/18] drm/i915/gtt: Only keep gen6 page directories pinned while active Chris Wilson
2018-06-08 12:55 ` [PATCH 10/18] drm/i915/gtt: Lazily allocate page directories for gen7 Chris Wilson
2018-06-08 14:37   ` Matthew Auld
2018-06-08 14:43     ` Chris Wilson
2018-06-08 12:55 ` [PATCH 11/18] drm/i915/gtt: Free unused page tables on unbind the context Chris Wilson
2018-06-08 12:55 ` [PATCH 12/18] drm/i915/gtt: Skip initializing PT with scratch if full Chris Wilson
2018-06-08 12:55 ` [PATCH 13/18] drm/i915/gtt: Cache the PTE encoding of the scratch page Chris Wilson
2018-06-08 12:55 ` [PATCH 14/18] drm/i915/gtt: Reduce a pair of runtime asserts Chris Wilson
2018-06-08 12:55 ` [PATCH 15/18] drm/i915/gtt: Skip clearing the GGTT under gen6+ full-ppgtt Chris Wilson
2018-06-08 12:56 ` [PATCH 16/18] drm/i915/gtt: Remove redundant hsw_mm_switch() Chris Wilson
2018-06-08 14:03   ` Mika Kuoppala
2018-06-08 12:56 ` [PATCH 17/18] drm/i915/gtt: Remove vgpu check for gen6 Chris Wilson
2018-06-08 14:06   ` Mika Kuoppala
2018-06-08 12:56 ` [PATCH 18/18] RFT drm/i915/gtt: Enable full-ppgtt by default everywhere Chris Wilson
2018-06-08 13:25 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/18] drm/i915: Apply batch location restrictions before pinning (rev2) Patchwork
2018-06-08 13:30 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-06-08 13:41 ` ✓ Fi.CI.BAT: success " Patchwork
2018-06-08 16:23 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-06-08 16:36   ` Chris Wilson
2018-06-08 17:09     ` Chris Wilson
2018-06-08 18:03 ` ✗ Fi.CI.BAT: failure for series starting with [01/18] drm/i915: Apply batch location restrictions before pinning (rev3) 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=874lidxu5u.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@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