From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Lock out execlist tasklet while peeking inside for busy-stats
Date: Mon, 15 Jan 2018 09:56:12 +0000 [thread overview]
Message-ID: <87519b0e-f0cc-44ee-71c5-8ee528df8fd0@linux.intel.com> (raw)
In-Reply-To: <20180115092041.13509-1-chris@chris-wilson.co.uk>
On 15/01/2018 09:20, Chris Wilson wrote:
> In order to prevent a race condition where we may end up overaccounting
> the active state and leaving the busy-stats believing the GPU is 100%
> busy, lock out the tasklet while we reconstruct the busy state. There is
> no direct spinlock guard for the execlists->port[], so we need to
> utilise tasklet_disable() as a synchronous barrier to prevent the only
> writer to execlists->port[] from running at the same time as the enable.
>
> Fixes: 4900727d35bb ("drm/i915/pmu: Reconstruct active state on starting busy-stats")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/intel_engine_cs.c | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
> index d790bdc227ff..b221610f2365 100644
> --- a/drivers/gpu/drm/i915/intel_engine_cs.c
> +++ b/drivers/gpu/drm/i915/intel_engine_cs.c
> @@ -1943,16 +1943,22 @@ intel_engine_lookup_user(struct drm_i915_private *i915, u8 class, u8 instance)
> */
> int intel_enable_engine_stats(struct intel_engine_cs *engine)
> {
> + struct intel_engine_execlists *execlists = &engine->execlists;
> unsigned long flags;
> + int err = 0;
>
> if (!intel_engine_supports_stats(engine))
> return -ENODEV;
>
> + tasklet_disable(&execlists->tasklet);
> spin_lock_irqsave(&engine->stats.lock, flags);
> - if (engine->stats.enabled == ~0)
> - goto busy;
> +
> + if (unlikely(engine->stats.enabled == ~0)) {
> + err = -EBUSY;
> + goto unlock;
> + }
> +
> if (engine->stats.enabled++ == 0) {
> - struct intel_engine_execlists *execlists = &engine->execlists;
> const struct execlist_port *port = execlists->port;
> unsigned int num_ports = execlists_num_ports(execlists);
>
> @@ -1967,14 +1973,12 @@ int intel_enable_engine_stats(struct intel_engine_cs *engine)
> if (engine->stats.active)
> engine->stats.start = engine->stats.enabled_at;
> }
> - spin_unlock_irqrestore(&engine->stats.lock, flags);
>
> - return 0;
> -
> -busy:
> +unlock:
> spin_unlock_irqrestore(&engine->stats.lock, flags);
> + tasklet_enable(&execlists->tasklet);
>
> - return -EBUSY;
> + return err;
> }
>
> static ktime_t __intel_engine_get_busy_time(struct intel_engine_cs *engine)
>
Hopefully the end of the immediate trouble, with only beautification
remaining.
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:[~2018-01-15 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 9:20 [PATCH] drm/i915: Lock out execlist tasklet while peeking inside for busy-stats Chris Wilson
2018-01-15 9:56 ` Tvrtko Ursulin [this message]
2018-01-15 10:39 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-15 12:11 ` ✓ Fi.CI.IGT: " Patchwork
2018-01-15 12:25 ` 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=87519b0e-f0cc-44ee-71c5-8ee528df8fd0@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