public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: don't track relative-constants-mode
Date: Wed, 7 Sep 2016 18:44:31 +0100	[thread overview]
Message-ID: <2f695c30-da26-afcd-e872-2de63eb5db22@intel.com> (raw)
In-Reply-To: <20160826195557.GC23484@nuc-i3427.alporthouse.com>

On 26/08/16 20:55, Chris Wilson wrote:
> On Fri, Aug 26, 2016 at 08:46:25PM +0100, Dave Gordon wrote:
>> @@ -1520,6 +1528,14 @@ static void eb_export_fence(struct drm_i915_gem_object *obj,
>>  	if (ret)
>>  		return ret;
>>
>> +	if (instp_mode != I915_EXEC_CONSTANTS_REL_GENERAL) {
>> +		/* Restore default value of INSTPM */
>> +		ret = emit_instpm(params->request, instp_mask,
>> +				  I915_EXEC_CONSTANTS_REL_GENERAL);
>> +		if (ret)
>> +			return ret;
>
> We can't return an error at this point, we are committed to executing
> the batch. And we do expect to see at least an EINTR here occasionally.
> -Chris

Note the 'if (ret) return ret' just above. We already quit early on 
error, this just adds yet one more case. If you want to throw 
half-formed command streams at the GPU you'll need to fix all the other 
early exits, so adding one more doesn't really make it any worse.

In any case, it's the result from the ring_begin() which universally 
triggers an early exit, but on the other hand should never fail because 
we reserved enough space up front.

.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-09-07 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 19:46 [PATCH v2] drm/i915: don't track relative-constants-mode Dave Gordon
2016-08-26 19:55 ` Chris Wilson
2016-09-07 17:44   ` Dave Gordon [this message]

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=2f695c30-da26-afcd-e872-2de63eb5db22@intel.com \
    --to=david.s.gordon@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