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
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH 2/4] drm/i915/execlists: Pause CS flow before reset
Date: Tue, 31 Mar 2020 16:08:54 +0300	[thread overview]
Message-ID: <87ftdopt7d.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200331091459.29179-2-chris@chris-wilson.co.uk>

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

> Since we may be attempting to reset an active engine, we try to freeze
> it in place before resetting -- to be on the safe side. We can go one
> step further if we are using the CS flow semaphore to prevent the
> context switching into the next.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>

> ---
>  drivers/gpu/drm/i915/gt/intel_lrc.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index 9fff4e02cee6..9e18c0896a83 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -3669,6 +3669,7 @@ static void execlists_reset_prepare(struct intel_engine_cs *engine)
>  	 *
>  	 * FIXME: Wa for more modern gens needs to be validated
>  	 */
> +	ring_set_paused(engine, 1);
>  	intel_engine_stop_cs(engine);
>  }
>  
> -- 
> 2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-03-31 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  9:14 [Intel-gfx] [PATCH 1/4] drm/i915/selftests: Tidy up an error message for live_error_interrupt Chris Wilson
2020-03-31  9:14 ` [Intel-gfx] [PATCH 2/4] drm/i915/execlists: Pause CS flow before reset Chris Wilson
2020-03-31 13:08   ` Mika Kuoppala [this message]
2020-03-31  9:14 ` [Intel-gfx] [PATCH 3/4] drm/i915/execlists: Peek at the next submission for error interrupts Chris Wilson
2020-03-31  9:14 ` [Intel-gfx] [PATCH 4/4] drm/i915/execlists: Record the active CCID from before reset Chris Wilson
2020-03-31 11:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915/selftests: Tidy up an error message for live_error_interrupt Patchwork
2020-03-31 13:07 ` [Intel-gfx] [PATCH 1/4] " Mika Kuoppala
2020-04-01  8:34 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/4] " 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=87ftdopt7d.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