public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org,
	Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH v3 1/2] drm/i915: Move engine->submit_request selection to a vfunc
Date: Wed, 15 Mar 2017 08:14:04 +0000	[thread overview]
Message-ID: <7cee577b-8e48-d4bd-0b92-adc01a74fed7@linux.intel.com> (raw)
In-Reply-To: <20170314213342.GO2118@nuc-i3427.alporthouse.com>


On 14/03/2017 21:33, Chris Wilson wrote:
> On Tue, Mar 14, 2017 at 04:31:58PM +0000, Tvrtko Ursulin wrote:
>>
>> On 14/03/2017 09:34, Chris Wilson wrote:
>>> It turns out that we may want to restore the original
>>> engine->submit_request (and engine->schedule) callbacks from more than
>>> just the guc <-> execlists transition. Move this to a vfunc so we can
>>> have a common interface.
>>>
>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/i915_guc_submission.c |  2 +-
>>> drivers/gpu/drm/i915/intel_engine_cs.c     | 10 ++++++++++
>>> drivers/gpu/drm/i915/intel_lrc.c           | 15 +++++----------
>>> drivers/gpu/drm/i915/intel_lrc.h           |  1 -
>>> drivers/gpu/drm/i915/intel_ringbuffer.c    | 15 +++++++++++++--
>>> drivers/gpu/drm/i915/intel_ringbuffer.h    |  4 ++++
>>> 6 files changed, 33 insertions(+), 14 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_guc_submission.c b/drivers/gpu/drm/i915/i915_guc_submission.c
>>> index b4d24cd7639a..119b5c073833 100644
>>> --- a/drivers/gpu/drm/i915/i915_guc_submission.c
>>> +++ b/drivers/gpu/drm/i915/i915_guc_submission.c
>>> @@ -1051,7 +1051,7 @@ void i915_guc_submission_disable(struct drm_i915_private *dev_priv)
>>> 		return;
>>>
>>> 	/* Revert back to manual ELSP submission */
>>> -	intel_execlists_enable_submission(dev_priv);
>>> +	intel_engines_enable_submission(dev_priv);
>>
>> intel_engines_default_submission came to my mind but that will also
>> be misleading once the guc switch is toggled. But I think less
>> misleading than enable_submission. And vfunc name maybe as
>> assign_default_submission?
>
> intel_engines_reset_default_submission
> engine->set_default_submission
>
> Not overly enamoured, but the above seems like the best compromise so
> far.

Sounds good.

>>> }
>>>
>>> void i915_guc_submission_fini(struct drm_i915_private *dev_priv)
>>> diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
>>> index 73fe718516a5..5663ebab851f 100644
>>> --- a/drivers/gpu/drm/i915/intel_engine_cs.c
>>> +++ b/drivers/gpu/drm/i915/intel_engine_cs.c
>>> @@ -191,6 +191,7 @@ int intel_engines_init(struct drm_i915_private *dev_priv)
>>> 			goto cleanup;
>>> 		}
>>>
>>> +		engine->enable_submission(engine);
>>
>> Could be moved to intel_engines_setup_common if the
>> logical_ring_setup was re-arranged a bit so that the default_vfuncs
>> are assigned before it. Legacy looks like it would be alright with
>> that approach already.
>>
>> My thinking here is not to expose this vfunc so prominently in the
>> code since it is a bit of a low level internal implementation thing.
>
> The concern is reasonable, but equally moving it to
> intel_engine_setup_common() is hairy. Otoh, I think it is suitable for
> intel_engine_init_common(). Happy?

Why do you think it is hairy for intel_engine_setup_common? It keeps the 
setup/init split for lrc, where all vfuncs are initialized in the setup 
phase which was the intention.

Legacy is a bit more uncleanly split now that I look at it, but putting 
it at intel_engine_init_common would be just more of the same.

Regards,

Tvrtko



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

  reply	other threads:[~2017-03-15  8:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14  9:34 [PATCH v3 1/2] drm/i915: Move engine->submit_request selection to a vfunc Chris Wilson
2017-03-14  9:34 ` [PATCH v3 2/2] drm/i915: Restore engine->submit_request before unwedging Chris Wilson
2017-03-15  9:23   ` Tvrtko Ursulin
2017-03-15  9:34     ` Chris Wilson
2017-03-15 10:04       ` Tvrtko Ursulin
2017-03-14 16:17 ` ✓ Fi.CI.BAT: success for series starting with [v3,1/2] drm/i915: Move engine->submit_request selection to a vfunc Patchwork
2017-03-14 16:31 ` [PATCH v3 1/2] " Tvrtko Ursulin
2017-03-14 21:33   ` Chris Wilson
2017-03-15  8:14     ` Tvrtko Ursulin [this message]
2017-03-15  9:41       ` Chris Wilson
2017-03-15 10:05         ` Tvrtko Ursulin

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=7cee577b-8e48-d4bd-0b92-adc01a74fed7@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@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