public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	Intel-gfx@lists.freedesktop.org
Subject: Re: [RFC 00/17] Per-context and per-client engine busyness
Date: Fri, 27 Oct 2017 01:12:11 +0100	[thread overview]
Message-ID: <bc7336df-6d37-bc3a-1c70-fb1f52ed8d92@intel.com> (raw)
In-Reply-To: <150904871643.2864.9301646039900758151@mail.alporthouse.com>

On 26/10/17 21:11, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2017-10-26 18:13:13)
>> On 26/10/17 14:05, Chris Wilson wrote:
>>> Quoting Tvrtko Ursulin (2017-10-26 14:00:28)
>>>> On 26/10/2017 10:50, Lionel Landwerlin wrote:
>>>>> On 26/10/17 08:34, Tvrtko Ursulin wrote:
>>>>>> On 25/10/2017 18:38, Chris Wilson wrote:
>>>>>>> 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>
>>>>>>>> I've prototyped a quick demo of intel-client-top which produces
>>>>>>>> output like:
>>>>>>>>
>>>>>>>>         neverball[  6011]:  rcs0:  41.01%  bcs0:   0.00%  vcs0:
>>>>>>>> 0.00%  vecs0:   0.00%
>>>>>>>>              Xorg[  5664]:  rcs0:  31.16%  bcs0:   0.00%  vcs0:
>>>>>>>> 0.00%  vecs0:   0.00%
>>>>>>>>             xfwm4[  5727]:  rcs0:   0.00%  bcs0:   0.00%  vcs0:
>>>>>>>> 0.00%  vecs0:   0.00%
>>>>>>> +1
>>>>>>> +2 for a graph ;)
>>>>>> Where are those placement students when you need them! :)
>>>>> I won't be your student, but I could like to wire this into gputop.
>>>> I was thinking gputop as well but did find the time to look at it yet.
>>> We don't even ship gputop or the perf generator in igt... Can we at
>>> least make noises towards owning that code...
>>> -Chris
>>>
>> It would be nice to have stuff in single repo but gputop has quite a few
>> dependencies that I'm not sure igt will want.
> Just add the dependencies as optional to the build scripts; we don't
> have to add them to the common libs or make them mandatory except if we
> want to build all the tools. (If they are that bad, just pull it in as a
> submodule.) But it would be nice to exploit the synergies between the
> existing tools and test/perf harnesses; even if long term ubergpuprofiler
> takes over as the defacto tool for all gpus.
>
> And we have to purge the current intel_gpu_top; killing machines since
> 2011.
> -Chris
>

It's just a massive amount of deps right now.
Including: node, emscripten, protobuf, a websocket lib, libuv and more.
I also had the good taste of pulling in some bits of mesa for the device 
descriptions (which contains bits that igt doesn't have).
It's hard to look forward to improve all of that when there are cool 
features to implement.

Completely agree on the synergy part. I'll try to work towards that.

-
Lionel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-10-27  0:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 15:36 [RFC 00/17] Per-context and per-client engine busyness Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 01/17] drm/i915: Extract intel_get_cagf Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 02/17] drm/i915/pmu: Expose a PMU interface for perf queries Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 03/17] drm/i915/pmu: Suspend sampling when GPU is idle Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 04/17] drm/i915: Wrap context schedule notification Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 05/17] drm/i915: Engine busy time tracking Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 06/17] drm/i915/pmu: Wire up engine busy stats to PMU Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 07/17] drm/i915/pmu: Add interrupt count metric Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 08/17] drm/i915: Convert intel_rc6_residency_us to ns Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 09/17] drm/i915/pmu: Add RC6 residency metrics Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 10/17] drm/i915: Keep a count of requests waiting for a slot on GPU Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 11/17] drm/i915/pmu: Add queued counter Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 12/17] drm/i915: Track per-context engine busyness Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 13/17] drm/i915: Allow clients to query own per-engine busyness Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 14/17] drm/i915: Expose list of clients in sysfs Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 15/17] drm/i915: Update client name on context create Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 16/17] drm/i915: Expose per-engine client busyness Tvrtko Ursulin
2017-10-25 15:36 ` [RFC 17/17] drm/i915: Add sysfs toggle to enable per-client engine stats Tvrtko Ursulin
2017-10-25 15:47 ` [RFC 00/17] Per-context and per-client engine busyness Chris Wilson
2017-10-25 17:38   ` Chris Wilson
2017-10-26  7:34     ` Tvrtko Ursulin
2017-10-26  7:51       ` Chris Wilson
2017-10-26  9:50       ` Lionel Landwerlin
2017-10-26 10:10         ` Chris Wilson
2017-10-26 13:00         ` Tvrtko Ursulin
2017-10-26 13:05           ` Chris Wilson
2017-10-26 17:13             ` Lionel Landwerlin
2017-10-26 20:11               ` Chris Wilson
2017-10-27  0:12                 ` Lionel Landwerlin [this message]
2017-10-25 17:06 ` ✗ Fi.CI.BAT: failure for " 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=bc7336df-6d37-bc3a-1c70-fb1f52ed8d92@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=tursulin@ursulin.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox