From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 16/21] drm/i915: Move idle barrier cleanup into engine-pm
Date: Fri, 20 Sep 2019 17:18:08 +0100 [thread overview]
Message-ID: <0e7ace14-650b-aa16-8a7b-5afd37fdb690@linux.intel.com> (raw)
In-Reply-To: <20190902040303.14195-16-chris@chris-wilson.co.uk>
On 02/09/2019 05:02, Chris Wilson wrote:
> Now that we now longer need to guarantee that the active callback is
> under the struct_mutex, we can lift it out of the i915_gem_park() and
> into the engine parking itself.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_pm.c | 19 -------------------
> drivers/gpu/drm/i915/gt/intel_engine_pm.c | 15 +++++++++++++++
> drivers/gpu/drm/i915/i915_active.c | 1 +
> 3 files changed, 16 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_pm.c b/drivers/gpu/drm/i915/gem/i915_gem_pm.c
> index 92558fa47108..6e4cc177cc7a 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_pm.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_pm.c
> @@ -11,29 +11,10 @@
> #include "i915_drv.h"
> #include "i915_globals.h"
>
> -static void call_idle_barriers(struct intel_engine_cs *engine)
> -{
> - struct llist_node *node, *next;
> -
> - llist_for_each_safe(node, next, llist_del_all(&engine->barrier_tasks)) {
> - struct dma_fence_cb *cb =
> - container_of((struct list_head *)node,
> - typeof(*cb), node);
> -
> - cb->func(NULL, cb);
> - }
> -}
> -
> static void i915_gem_park(struct drm_i915_private *i915)
> {
> - struct intel_engine_cs *engine;
> - enum intel_engine_id id;
> -
> lockdep_assert_held(&i915->drm.struct_mutex);
>
> - for_each_engine(engine, i915, id)
> - call_idle_barriers(engine); /* cleanup after wedging */
> -
> i915_vma_parked(i915);
>
> i915_globals_park();
> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_pm.c b/drivers/gpu/drm/i915/gt/intel_engine_pm.c
> index 65b5ca74b394..472b2259f629 100644
> --- a/drivers/gpu/drm/i915/gt/intel_engine_pm.c
> +++ b/drivers/gpu/drm/i915/gt/intel_engine_pm.c
> @@ -123,6 +123,19 @@ static bool switch_to_kernel_context(struct intel_engine_cs *engine)
> return result;
> }
>
> +static void call_idle_barriers(struct intel_engine_cs *engine)
> +{
> + struct llist_node *node, *next;
> +
> + llist_for_each_safe(node, next, llist_del_all(&engine->barrier_tasks)) {
> + struct dma_fence_cb *cb =
> + container_of((struct list_head *)node,
> + typeof(*cb), node);
> +
> + cb->func(NULL, cb);
> + }
> +}
> +
> static int __engine_park(struct intel_wakeref *wf)
> {
> struct intel_engine_cs *engine =
> @@ -142,6 +155,8 @@ static int __engine_park(struct intel_wakeref *wf)
>
> GEM_TRACE("%s\n", engine->name);
>
> + call_idle_barriers(engine); /* cleanup after wedging */
> +
> intel_engine_disarm_breadcrumbs(engine);
> intel_engine_pool_park(&engine->pool);
>
> diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c
> index 2e2ab8176620..dcf5bc1d87e6 100644
> --- a/drivers/gpu/drm/i915/i915_active.c
> +++ b/drivers/gpu/drm/i915/i915_active.c
> @@ -679,6 +679,7 @@ void i915_active_acquire_barrier(struct i915_active *ref)
> rb_link_node(&node->node, parent, p);
> rb_insert_color(&node->node, &ref->tree);
>
> + GEM_BUG_ON(!intel_engine_pm_is_awake(engine));
> llist_add(barrier_to_ll(node), &engine->barrier_tasks);
> intel_engine_pm_put(engine);
> }
>
If the rest plays out this is simple. :)
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-20 16:18 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 4:02 [PATCH 01/21] drm/i915: Restrict the aliasing-ppgtt to the size of the ggtt Chris Wilson
2019-09-02 4:02 ` [PATCH 02/21] drm/i915: Report aliasing ppgtt size as ggtt size Chris Wilson
2019-09-02 8:55 ` Matthew Auld
2019-09-02 4:02 ` [PATCH 03/21] drm/i915/execlists: Ignore lost completion events Chris Wilson
2019-09-02 4:02 ` [PATCH 04/21] drm/i915: Refresh the errno to vmf_fault translations Chris Wilson
2019-09-03 15:34 ` Abdiel Janulgue
2019-09-02 4:02 ` [PATCH 05/21] drm/i915: Replace obj->pin_global with obj->frontbuffer Chris Wilson
2019-09-02 4:02 ` [PATCH 06/21] dma-fence: Serialise signal enabling (dma_fence_enable_sw_signaling) Chris Wilson
2019-09-02 4:02 ` [PATCH 07/21] drm/mm: Pack allocated/scanned boolean into a bitfield Chris Wilson
2019-09-02 4:02 ` [PATCH 08/21] drm/i915: Make shrink/unshrink be atomic Chris Wilson
2019-09-10 19:54 ` Matthew Auld
2019-09-02 4:02 ` [PATCH 09/21] drm/i915: Only track bound elements of the GTT Chris Wilson
2019-09-02 4:02 ` [PATCH 10/21] drm/i915: Make i915_vma.flags atomic_t for mutex reduction Chris Wilson
2019-09-10 20:06 ` Matthew Auld
2019-09-02 4:02 ` [PATCH 11/21] drm/i915/gtt: Make sure the gen6 ppgtt is bound before first use Chris Wilson
2019-09-10 20:17 ` Matthew Auld
2019-09-02 4:02 ` [PATCH 12/21] drm/i915: Mark up address spaces that may need to allocate Chris Wilson
2019-09-20 16:22 ` Tvrtko Ursulin
2019-09-20 16:35 ` Chris Wilson
2019-09-23 8:10 ` Tvrtko Ursulin
2019-09-25 8:23 ` Chris Wilson
2019-09-25 15:59 ` Tvrtko Ursulin
2019-09-27 17:03 ` Chris Wilson
2019-09-02 4:02 ` [PATCH 13/21] drm/i915: Pull i915_vma_pin under the vm->mutex Chris Wilson
2019-09-16 10:13 ` Tvrtko Ursulin
2019-09-16 11:10 ` Chris Wilson
2019-09-17 12:37 ` Tvrtko Ursulin
2019-09-17 18:56 ` Chris Wilson
2019-09-19 13:37 ` Tvrtko Ursulin
2019-09-19 14:05 ` Chris Wilson
2019-09-02 4:02 ` [PATCH 14/21] drm/i915: Push the i915_active.retire into a worker Chris Wilson
2019-09-02 4:02 ` [PATCH 15/21] drm/i915: Coordinate i915_active with its own mutex Chris Wilson
2019-09-20 16:14 ` Tvrtko Ursulin
2019-09-20 16:32 ` Chris Wilson
2019-09-02 4:02 ` [PATCH 16/21] drm/i915: Move idle barrier cleanup into engine-pm Chris Wilson
2019-09-20 16:18 ` Tvrtko Ursulin [this message]
2019-09-02 4:02 ` [PATCH 17/21] drm/i915: Drop struct_mutex from around i915_retire_requests() Chris Wilson
2019-09-24 15:25 ` Tvrtko Ursulin
2019-09-25 8:43 ` Chris Wilson
2019-09-25 8:49 ` Tvrtko Ursulin
2019-09-02 4:03 ` [PATCH 18/21] drm/i915: Remove the GEM idle worker Chris Wilson
2019-09-24 15:26 ` Tvrtko Ursulin
2019-09-02 4:03 ` [PATCH 19/21] drm/i915: Merge wait_for_timelines with retire_request Chris Wilson
2019-09-24 15:57 ` Tvrtko Ursulin
2019-09-25 8:54 ` Chris Wilson
2019-09-02 4:03 ` [PATCH 20/21] drm/i915: Move request runtime management onto gt Chris Wilson
2019-09-02 4:03 ` [PATCH 21/21] drm/i915: Move global activity tracking from GEM to GT Chris Wilson
2019-09-25 9:55 ` Tvrtko Ursulin
2019-09-02 4:54 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/21] drm/i915: Restrict the aliasing-ppgtt to the size of the ggtt Patchwork
2019-09-02 5:20 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-02 8:00 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-09-02 8:52 ` [PATCH 01/21] " Matthew Auld
-- strict thread matches above, loose matches on Subject: below --
2019-08-30 6:11 [PATCH 01/21] drm/i915/gtt: Downgrade Baytrail back to aliasing-ppgtt Chris Wilson
2019-08-30 6:11 ` [PATCH 16/21] drm/i915: Move idle barrier cleanup into engine-pm 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=0e7ace14-650b-aa16-8a7b-5afd37fdb690@linux.intel.com \
--to=tvrtko.ursulin@linux.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