From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915/execlists: Assert tasklet is locked for process_csb()
Date: Mon, 14 Oct 2019 10:43:20 +0100 [thread overview]
Message-ID: <7a6bcc0e-588d-5354-d80b-aa4533d4c7eb@linux.intel.com> (raw)
In-Reply-To: <20191014093706.26325-1-chris@chris-wilson.co.uk>
On 14/10/2019 10:37, Chris Wilson wrote:
> We rely on only the tasklet being allowed to call into process_csb(), so
> assert that is locked when we do. As the tasklet uses a simple bitlock,
> there is no strong lockdep checking so we must make do with a plain
> assertion that the tasklet is running and assume that we are the
> tasklet!
>
> v2: Fixup intel_gt_sanitize() to prepare each engine for the reset so
> that the locks are marked as held during the reset
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_gt_pm.c | 11 ++++++++---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 1 +
> drivers/gpu/drm/i915/i915_gem.h | 5 +++++
> 3 files changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_pm.c b/drivers/gpu/drm/i915/gt/intel_gt_pm.c
> index 87e34e0b6427..bfc611f48ed6 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt_pm.c
> +++ b/drivers/gpu/drm/i915/gt/intel_gt_pm.c
> @@ -136,11 +136,16 @@ void intel_gt_sanitize(struct intel_gt *gt, bool force)
>
> intel_uc_sanitize(>->uc);
>
> - if (!reset_engines(gt) && !force)
> - return;
> + for_each_engine(engine, gt->i915, id)
> + engine->reset.prepare(engine);
> +
> + if (reset_engines(gt) || force) {
> + for_each_engine(engine, gt->i915, id)
> + __intel_engine_reset(engine, false);
> + }
>
> for_each_engine(engine, gt->i915, id)
> - __intel_engine_reset(engine, false);
> + engine->reset.finish(engine);
> }
>
> void intel_gt_pm_disable(struct intel_gt *gt)
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index 16b878d35814..fc4be76b3070 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -1843,6 +1843,7 @@ static void process_csb(struct intel_engine_cs *engine)
> u8 head, tail;
>
> GEM_BUG_ON(USES_GUC_SUBMISSION(engine->i915));
> + GEM_BUG_ON(!tasklet_is_locked(&execlists->tasklet));
>
> /*
> * Note that csb_write, csb_status may be either in HWSP or mmio.
> diff --git a/drivers/gpu/drm/i915/i915_gem.h b/drivers/gpu/drm/i915/i915_gem.h
> index db20d2b0842b..f6f9675848b8 100644
> --- a/drivers/gpu/drm/i915/i915_gem.h
> +++ b/drivers/gpu/drm/i915/i915_gem.h
> @@ -86,6 +86,11 @@ static inline void tasklet_lock(struct tasklet_struct *t)
> cpu_relax();
> }
>
> +static inline bool tasklet_is_locked(const struct tasklet_struct *t)
> +{
> + return test_bit(TASKLET_STATE_RUN, &t->state);
> +}
> +
> static inline void __tasklet_disable_sync_once(struct tasklet_struct *t)
> {
> if (!atomic_fetch_inc(&t->count))
>
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-10-14 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 19:31 [PATCH] drm/i915/execlists: Assert tasklet is locked for process_csb() Chris Wilson
2019-10-14 9:25 ` Tvrtko Ursulin
2019-10-14 9:27 ` Chris Wilson
2019-10-14 9:28 ` Chris Wilson
2019-10-14 9:31 ` Chris Wilson
2019-10-14 9:37 ` [PATCH v2] " Chris Wilson
2019-10-14 9:43 ` Tvrtko Ursulin [this message]
2019-10-14 11:42 ` [PATCH v3] " Chris Wilson
2019-10-14 12:13 ` Chris Wilson
2019-10-14 17:47 ` ✓ Fi.CI.BAT: success for drm/i915/execlists: Assert tasklet is locked for process_csb() (rev4) Patchwork
2019-10-15 2:28 ` ✓ Fi.CI.IGT: " Patchwork
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=7a6bcc0e-588d-5354-d80b-aa4533d4c7eb@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