From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Michel Thierry <michel.thierry@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/lrc: Prevent preemption when lite-restore is disabled
Date: Fri, 4 Sep 2015 17:15:42 +0100 [thread overview]
Message-ID: <55E9C3AE.3030906@intel.com> (raw)
In-Reply-To: <1441367955-22006-2-git-send-email-michel.thierry@intel.com>
On 04/09/15 12:59, Michel Thierry wrote:
> When WaEnableForceRestoreInCtxtDescForVCS is required, it is only
> safe to send new contexts if the last reported event is "active to
> idle". Otherwise the same context can fully preempt itself because
> lite-restore is disabled.
>
> Testcase: igt/gem_concurrent_blit
> Reported-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Signed-off-by: Michel Thierry <michel.thierry@intel.com>
> ---
The lock-up I was seeing goes away with these 2 patches applied, so:
Tested-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> drivers/gpu/drm/i915/intel_lrc.c | 24 ++++++++++++++++++------
> 1 file changed, 18 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
> index d8b605f..c3fca4b 100644
> --- a/drivers/gpu/drm/i915/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/intel_lrc.c
> @@ -277,10 +277,18 @@ u32 intel_execlists_ctx_id(struct drm_i915_gem_object *ctx_obj)
> return lrca >> 12;
> }
>
> +static bool disable_lite_restore_wa(struct intel_engine_cs *ring)
> +{
> + struct drm_device *dev = ring->dev;
> +
> + return ((IS_SKYLAKE(dev) && INTEL_REVID(dev) <= SKL_REVID_B0) ||
> + (IS_BROXTON(dev) && INTEL_REVID(dev) == BXT_REVID_A0)) &&
> + (ring->id == VCS || ring->id == VCS2);
> +}
> +
> uint64_t intel_lr_context_descriptor(struct intel_context *ctx,
> struct intel_engine_cs *ring)
> {
> - struct drm_device *dev = ring->dev;
> struct drm_i915_gem_object *ctx_obj = ctx->engine[ring->id].state;
> uint64_t desc;
> uint64_t lrca = i915_gem_obj_ggtt_offset(ctx_obj) +
> @@ -302,9 +310,7 @@ uint64_t intel_lr_context_descriptor(struct intel_context *ctx,
>
> /* WaEnableForceRestoreInCtxtDescForVCS:skl */
> /* WaEnableForceRestoreInCtxtDescForVCS:bxt */
> - if (((IS_SKYLAKE(dev) && INTEL_REVID(dev) <= SKL_REVID_B0) ||
> - (IS_BROXTON(dev) && INTEL_REVID(dev) == BXT_REVID_A0)) &&
> - (ring->id == VCS || ring->id == VCS2))
> + if (disable_lite_restore_wa(ring))
> desc |= GEN8_CTX_FORCE_RESTORE;
>
> return desc;
> @@ -495,7 +501,7 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring)
> u32 status_pointer;
> u8 read_pointer;
> u8 write_pointer;
> - u32 status;
> + u32 status = 0;
> u32 status_id;
> u32 submit_contexts = 0;
>
> @@ -533,8 +539,14 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring)
> }
> }
>
> - if (submit_contexts != 0)
> + if (disable_lite_restore_wa(ring)) {
> + /* Prevent a ctx to preempt itself */
> + if ((status & GEN8_CTX_STATUS_ACTIVE_IDLE) &&
> + (submit_contexts != 0))
> + execlists_context_unqueue(ring);
> + } else if (submit_contexts != 0) {
> execlists_context_unqueue(ring);
> + }
>
> spin_unlock(&ring->execlist_lock);
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-09-04 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 11:59 [PATCH 1/2] drm/i915: WaEnableForceRestoreInCtxtDescForVCS is for video engines only Michel Thierry
2015-09-04 11:59 ` [PATCH 2/2] drm/i915/lrc: Prevent preemption when lite-restore is disabled Michel Thierry
2015-09-04 16:15 ` Daniele Ceraolo Spurio [this message]
2015-09-10 17:37 ` Arun Siluvery
2015-09-14 8:25 ` Daniel Vetter
2015-09-10 17:34 ` [PATCH 1/2] drm/i915: WaEnableForceRestoreInCtxtDescForVCS is for video engines only Arun Siluvery
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=55E9C3AE.3030906@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michel.thierry@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