Re: [RFC 00/17] Per-context and per-client engine busyness

Chris Wilson
2017-10-25T17:38:34Z

Quoting Chris Wilson (2017-10-25 16:47:13)
> Quoting Tvrtko Ursulin (2017-10-25 16:36:15)
> > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > Another potential use for the per-client infrastructure is tieing it up with
> > perf PMU. At the moment our perf PMU are global counters only. With the per-
> > client infrastructure it should be possible to make it work in the task mode as
> > well and so enable GPU busyness profiling of single tasks.
>
> ctx->pid can be misleading, as it set on creation, but the context can
> be transferred over fd to the real client. (Typically that applies to
> the default context, 0.)

Ok, I see that you update the pid when a new context is created. Still
have the likes of libva that may use DRI3 without creating a context
itself.

Back to the general niggle; I really would like to avoid adding custom
i915 interfaces for this, that should be a last resort if we can find no
way through e.g. perf.
-Chris