All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Intel-gfx@lists.freedesktop.org,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH 05/10] drm/i915: Track runtime spent in unreachable intel_contexts
Date: Wed, 18 Mar 2020 14:32:52 +0000	[thread overview]
Message-ID: <158454197252.6873.7587021909076621666@build.alporthouse.com> (raw)
In-Reply-To: <3565cd32-5dd8-0d45-ee55-fb4fb51aa7bd@linux.intel.com>

Quoting Tvrtko Ursulin (2020-03-18 14:13:14)
> 
> On 18/03/2020 13:55, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2020-03-18 12:11:34)
> >> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >>
> >> As contexts are abandoned we want to remember how much GPU time they used
> >> (per class) so later we can used it for smarter purposes.
> >>
> >> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >> ---
> >>   drivers/gpu/drm/i915/gem/i915_gem_context.c       | 13 ++++++++++++-
> >>   drivers/gpu/drm/i915/gem/i915_gem_context_types.h |  5 +++++
> >>   2 files changed, 17 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_context.c b/drivers/gpu/drm/i915/gem/i915_gem_context.c
> >> index 7c119a3a2cbd..5edf79ed6247 100644
> >> --- a/drivers/gpu/drm/i915/gem/i915_gem_context.c
> >> +++ b/drivers/gpu/drm/i915/gem/i915_gem_context.c
> >> @@ -257,7 +257,19 @@ static void free_engines_rcu(struct rcu_head *rcu)
> >>   {
> >>          struct i915_gem_engines *engines =
> >>                  container_of(rcu, struct i915_gem_engines, rcu);
> >> +       struct i915_gem_context *ctx = engines->ctx;
> >> +       struct i915_gem_engines_iter it;
> >> +       struct intel_context *ce;
> >> +
> >> +       /* Transfer accumulated runtime to the parent GEM context. */
> >> +       for_each_gem_engine(ce, engines, it) {
> >> +               unsigned int class = ce->engine->uabi_class;
> >>   
> >> +               GEM_BUG_ON(class >= ARRAY_SIZE(ctx->past_runtime));
> >> +               atomic64_add(ce->runtime.total, &ctx->past_runtime[class]);
> > 
> > Hmm, there's an odd situation where the free_engines_rcu could fire
> > before we do the final schedule_out of the context.
> > 
> > GEM_BUG_ON(intel_context_inflight(ce)) to see if that's being too
> > paranoid.
> 
> Deja vu.. have I forgotten to move this into intel_context_free while 
> the purpose of keeping ce->gem_context valid was exactly to enable that.

I would rather not have it in gt/ if possible. The delay should be
nominal at worst.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-03-18 14:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 12:11 [Intel-gfx] [PATCH 00/10] Per client engine busyness Tvrtko Ursulin
2020-03-18 12:11 ` [Intel-gfx] [PATCH 01/10] drm/i915: Expose list of clients in sysfs Tvrtko Ursulin
2020-03-18 12:11 ` [Intel-gfx] [PATCH 02/10] drm/i915: Update client name on context create Tvrtko Ursulin
2020-03-18 12:11 ` [Intel-gfx] [PATCH 03/10] drm/i915: Make GEM contexts track DRM clients Tvrtko Ursulin
2020-03-18 13:47   ` Chris Wilson
2020-03-18 12:11 ` [Intel-gfx] [PATCH 04/10] drm/i915: Use explicit flag to mark unreachable intel_context Tvrtko Ursulin
2020-03-18 13:49   ` Chris Wilson
2020-03-18 13:55     ` Tvrtko Ursulin
2020-03-18 12:11 ` [Intel-gfx] [PATCH 05/10] drm/i915: Track runtime spent in unreachable intel_contexts Tvrtko Ursulin
2020-03-18 13:55   ` Chris Wilson
2020-03-18 14:13     ` Tvrtko Ursulin
2020-03-18 14:32       ` Chris Wilson [this message]
2020-03-18 14:38         ` Tvrtko Ursulin
2020-03-18 14:48           ` Chris Wilson
2020-03-18 15:07             ` Chris Wilson
2020-03-18 12:11 ` [Intel-gfx] [PATCH 06/10] drm/i915: Track runtime spent in closed GEM contexts Tvrtko Ursulin
2020-03-18 13:57   ` Chris Wilson
2020-03-18 12:11 ` [Intel-gfx] [PATCH 07/10] drm/i915: Track all user contexts per client Tvrtko Ursulin
2020-03-18 12:11 ` [Intel-gfx] [PATCH 08/10] drm/i915: Expose per-engine client busyness Tvrtko Ursulin
2020-03-18 14:00   ` Chris Wilson
2020-03-18 14:15     ` Tvrtko Ursulin
2020-03-18 14:34       ` Chris Wilson
2020-04-15 10:19         ` Tvrtko Ursulin
2020-03-18 12:11 ` [Intel-gfx] [PATCH 09/10] drm/i915: Track context current active time 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=158454197252.6873.7587021909076621666@build.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.