From: Michel Thierry <michel.thierry@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Workaround to avoid lite restore with HEAD==TAIL
Date: Fri, 10 Apr 2015 11:14:32 +0100 [thread overview]
Message-ID: <5527A288.6000404@intel.com> (raw)
In-Reply-To: <20150410100108.GH6092@phenom.ffwll.local>
On 4/10/2015 11:01 AM, Daniel Vetter wrote:
> On Fri, Apr 10, 2015 at 10:32:33AM +0100, Michel Thierry wrote:
>> WaIdleLiteRestore is an execlists-only workaround, and requires the driver
>> to ensure that any context always has HEAD!=TAIL when attempting lite
>> restore.
>>
>> Add two extra MI_NOOP instructions at the end of each request, but keep
>> the requests tail pointing before the MI_NOOPs.
>>
>> If we submit a context to the ELSP which has previously been submitted,
>> move the tail pointer past the MI_NOOPs. This ensures HEAD!=TAIL.
>>
>> Signed-off-by: Thomas Daniel <thomas.daniel@intel.com>
>> Signed-off-by: Michel Thierry <michel.thierry@intel.com>
> Is there an igt to provoke this? I'm thinking of submitting tiny noop
> batches on 2 alternating contexts. That should be able to make this go
> boom pretty reliable, we only need a slight delay in processing the
> execlist completion interrupt.
> -Daniel
I've seen it when running multiple contexts in parallel or when the
wa-batchbuffer was enabled.
I'll write an igt for it, we only need several small batches queued to
trigger the light restore.
--Michel
>> ---
>> drivers/gpu/drm/i915/i915_gem.c | 11 +++++++++++
>> drivers/gpu/drm/i915/intel_lrc.c | 29 +++++++++++++++++++++++++++++
>> 2 files changed, 40 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
>> index ca522c9..a44070a 100644
>> --- a/drivers/gpu/drm/i915/i915_gem.c
>> +++ b/drivers/gpu/drm/i915/i915_gem.c
>> @@ -2382,6 +2382,17 @@ int __i915_add_request(struct intel_engine_cs *ring,
>> request->head = request_start;
>> request->tail = intel_ring_get_tail(ringbuf);
>>
>> + if (i915.enable_execlists &&
>> + (IS_GEN8(ring->dev) || IS_GEN9(ring->dev))) {
>> + /*
>> + * Here we add two extra NOOPs as padding to avoid
>> + * lite restore of a context with HEAD==TAIL.
>> + */
>> + intel_logical_ring_emit(ringbuf, MI_NOOP);
>> + intel_logical_ring_emit(ringbuf, MI_NOOP);
>> + intel_logical_ring_advance(ringbuf);
>> + }
>> +
>> /* Whilst this request exists, batch_obj will be on the
>> * active_list, and so will hold the active reference. Only when this
>> * request is retired will the the batch_obj be moved onto the
>> diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
>> index f18f96c..8acedca 100644
>> --- a/drivers/gpu/drm/i915/intel_lrc.c
>> +++ b/drivers/gpu/drm/i915/intel_lrc.c
>> @@ -413,6 +413,26 @@ static void execlists_context_unqueue(struct intel_engine_cs *ring)
>> }
>> }
>>
>> + if (IS_GEN8(ring->dev) || IS_GEN9(ring->dev)) {
>> + /*
>> + * WaIdleLiteRestore: make sure we never cause a lite
>> + * restore with HEAD==TAIL
>> + */
>> + if (req0 && req0->elsp_submitted == 1) {
>> + /*
>> + * Consume the buffer NOOPs to ensure HEAD != TAIL when
>> + * submitting. elsp_submitted can only be >1 after
>> + * reset, in which case we don't need the workaround as
>> + * a lite restore will not occur.
>> + */
>> + struct intel_ringbuffer *ringbuf;
>> +
>> + ringbuf = req0->ctx->engine[ring->id].ringbuf;
>> + req0->tail += 8;
>> + req0->tail &= ringbuf->size - 1;
>> + }
>> + }
>> +
>> WARN_ON(req1 && req1->elsp_submitted);
>>
>> execlists_submit_contexts(ring, req0->ctx, req0->tail,
>> @@ -829,6 +849,15 @@ static int intel_logical_ring_begin(struct intel_ringbuffer *ringbuf,
>> struct drm_i915_private *dev_priv = dev->dev_private;
>> int ret;
>>
>> + if (IS_GEN8(dev) || IS_GEN9(dev)) {
>> + /*
>> + * Reserve space for 2 NOOPs at the end of each request to be
>> + * used as a workaround for not being allowed to do lite
>> + * restore with HEAD==TAIL.
>> + */
>> + num_dwords += 2;
>> + }
>> +
>> ret = i915_gem_check_wedge(&dev_priv->gpu_error,
>> dev_priv->mm.interruptible);
>> if (ret)
>> --
>> 2.1.1
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-10 10:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 9:32 [PATCH] drm/i915: Workaround to avoid lite restore with HEAD==TAIL Michel Thierry
2015-04-10 10:01 ` Daniel Vetter
2015-04-10 10:11 ` Chris Wilson
2015-04-10 10:14 ` Michel Thierry [this message]
2015-04-14 6:08 ` shuang.he
2015-04-14 15:41 ` [PATCH v2] " Michel Thierry
2015-04-15 6:49 ` Chris Wilson
2015-04-15 19:04 ` shuang.he
2015-04-15 16:17 ` [PATCH v3] " Michel Thierry
2015-04-15 16:40 ` Chris Wilson
2015-04-15 17:08 ` Michel Thierry
2015-04-16 9:29 ` shuang.he
2015-04-15 17:11 ` [PATCH v4] " Michel Thierry
2015-04-15 17:19 ` Chris Wilson
2015-04-23 21:20 ` Jani Nikula
2015-04-16 14:07 ` shuang.he
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=5527A288.6000404@intel.com \
--to=michel.thierry@intel.com \
--cc=daniel@ffwll.ch \
--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