From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH 10/19] drm/i915: Rearrange switch_context to load the aliasing ppgtt on first use
Date: Thu, 21 Apr 2016 09:48:36 +0300 [thread overview]
Message-ID: <1461221316.4381.11.camel@linux.intel.com> (raw)
In-Reply-To: <1461177750-20187-11-git-send-email-chris@chris-wilson.co.uk>
On ke, 2016-04-20 at 19:42 +0100, Chris Wilson wrote:
> The code to switch_mm() is already handled by i915_switch_context(), the
> only difference required to setup the aliasing ppgtt is that we need to
> emit te switch_mm() on the first context, i.e. when transitioning from
> engine->last_context == NULL. This allows us to defer the
> initialisation of the GPU from early device initialisation to first use,
> which should marginally speed up both. The caveat is that we then defer
> the context initialisation until first use - i.e. we cannot assume that
> the GPU engines are initialised. For example, this means that power
> contexts for rc6 (Ironlake) need to explicitly loaded, as they are.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Some comments below.
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index aafcb4942acf..14c9b29294c5 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -4910,34 +4910,6 @@ i915_gem_init_hw(struct drm_device *dev)
> if (ret)
> goto out;
This whole if (ret) goto out can be removed as out is right after the
removed code block.
>
> - /* Now it is safe to go back round and do everything else: */
> - for_each_engine(engine, dev_priv) {
> - struct drm_i915_gem_request *req;
> -
> - req = i915_gem_request_alloc(engine, NULL);
> - if (IS_ERR(req)) {
> - ret = PTR_ERR(req);
> - break;
> - }
> -
> - ret = i915_ppgtt_init_ring(req);
> - if (ret)
> - goto err_request;
> -
> - ret = i915_gem_context_enable(req);
> - if (ret)
> - goto err_request;
> -
> -err_request:
> - i915_add_request_no_flush(req);
> - if (ret) {
> - DRM_ERROR("Failed to enable %s, error=%d\n",
> - engine->name, ret);
> - i915_gem_cleanup_engines(dev);
> - break;
> - }
> - }
> -
> out:
> intel_uncore_forcewake_put(dev_priv, FORCEWAKE_ALL);
> return ret;
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index e5b3d74f8222..4d376f984a8c 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -431,27 +431,6 @@ void i915_gem_context_fini(struct drm_device *dev)
> dev_priv->kernel_context = NULL;
> }
>
<SNIP>
>
> static bool
> -needs_pd_load_pre(struct intel_engine_cs *engine, struct intel_context *to)
> +needs_pd_load_pre(struct i915_hw_ppgtt *ppgtt,
> + struct intel_engine_cs *engine,
> + struct intel_context *to)
> {
> - if (!to->ppgtt)
> + if (ppgtt == NULL)
Code checker will scream and ask for !ppgtt. And I'm pretty sure we
should not keep flip-flopping between two styles. Also, you're not
doing != NULL either to check if pointer is not NULL, but just if
(foo), so I do not see why to avoid if (!foo).
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-21 6:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 18:42 Premature unpinning at last Chris Wilson
2016-04-20 18:42 ` [PATCH 01/19] drm/i915/overlay: Replace i915_gem_obj_ggtt_offset() with the known flip_addr Chris Wilson
2016-04-20 18:42 ` [PATCH 02/19] io-mapping: Specify mapping size for io_mapping_map_wc() Chris Wilson
2016-04-20 18:58 ` Luis R. Rodriguez
2016-04-20 19:14 ` Chris Wilson
2016-04-20 21:23 ` Luis R. Rodriguez
2016-04-20 18:42 ` [PATCH 03/19] drm/i915: Introduce i915_vm_to_ggtt() Chris Wilson
2016-04-20 18:42 ` [PATCH 04/19] drm/i915: Move ioremap_wc tracking onto VMA Chris Wilson
2016-04-20 18:42 ` [PATCH 05/19] drm/i915: Use i915_vma_pin_iomap on the ringbuffer object Chris Wilson
2016-04-21 7:19 ` Joonas Lahtinen
2016-04-20 18:42 ` [PATCH 06/19] drm/i915: Mark the current context as lost on suspend Chris Wilson
2016-04-20 18:42 ` [PATCH 07/19] drm/i915: L3 cache remapping is part of context switching Chris Wilson
2016-04-20 18:42 ` [PATCH 08/19] drm/i915: Consolidate L3 remapping LRI Chris Wilson
2016-04-20 18:42 ` [PATCH 09/19] drm/i915: Remove early l3-remap Chris Wilson
2016-04-20 18:42 ` [PATCH 10/19] drm/i915: Rearrange switch_context to load the aliasing ppgtt on first use Chris Wilson
2016-04-21 6:48 ` Joonas Lahtinen [this message]
2016-04-21 6:58 ` Chris Wilson
2016-04-21 7:01 ` Chris Wilson
2016-04-21 7:24 ` Chris Wilson
2016-04-21 7:32 ` Joonas Lahtinen
2016-04-20 18:42 ` [PATCH 11/19] drm/i915: Assign every HW context a unique ID Chris Wilson
2016-04-20 18:42 ` [PATCH 12/19] drm/i915: Replace the pinned context address with its " Chris Wilson
2016-04-20 18:42 ` [PATCH 13/19] drm/i915: Refactor execlists default context pinning Chris Wilson
2016-04-20 18:42 ` [PATCH 14/19] drm/i915: Move context initialisation to first-use Chris Wilson
2016-04-21 6:57 ` Joonas Lahtinen
2016-04-21 7:08 ` Chris Wilson
2016-04-21 7:47 ` Joonas Lahtinen
2016-04-21 7:56 ` Chris Wilson
2016-04-21 8:37 ` Joonas Lahtinen
2016-04-20 18:42 ` [PATCH 15/19] drm/i915: Move the magical deferred context allocation into the request Chris Wilson
2016-04-20 18:42 ` [PATCH 16/19] drm/i915: Move releasing of the GEM request from free to retire/cancel Chris Wilson
2016-04-20 18:42 ` [PATCH 17/19] drm/i915: Track the previous pinned context inside the request Chris Wilson
2016-04-21 7:07 ` Joonas Lahtinen
2016-04-21 7:22 ` Chris Wilson
2016-04-21 7:35 ` Joonas Lahtinen
2016-04-20 18:42 ` [PATCH 18/19] drm/i915: Store LRC hardware id in " Chris Wilson
2016-04-21 7:58 ` Tvrtko Ursulin
2016-04-21 9:02 ` Chris Wilson
2016-04-20 18:42 ` [PATCH 19/19] drm/i915: Stop tracking execlists retired requests Chris Wilson
2016-04-21 11:27 ` ✓ Fi.CI.BAT: success for series starting with [01/19] drm/i915/overlay: Replace i915_gem_obj_ggtt_offset() with the known flip_addr Patchwork
2016-04-21 12:05 ` ✗ Fi.CI.BAT: failure " Patchwork
2016-04-23 10:53 ` ✗ Fi.CI.BAT: warning " Patchwork
2016-04-25 6:51 ` Patchwork
-- strict thread matches above, loose matches on Subject: below --
2016-04-21 8:58 [PATCH 01/19] " Chris Wilson
2016-04-21 8:58 ` [PATCH 10/19] drm/i915: Rearrange switch_context to load the aliasing ppgtt on first use Chris Wilson
2016-04-21 14:57 Final CI pass for premature Chris Wilson
2016-04-21 14:57 ` [PATCH 10/19] drm/i915: Rearrange switch_context to load the aliasing ppgtt on first use Chris Wilson
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=1461221316.4381.11.camel@linux.intel.com \
--to=joonas.lahtinen@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