All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Intel-gfx@lists.freedesktop.org,
	Tvrtko Ursulin <tursulin@ursulin.net>
Subject: Re: [RFC 00/13] 21st century intel_gpu_top
Date: Wed, 3 Oct 2018 13:57:31 +0100	[thread overview]
Message-ID: <8de45bc3-00f6-892b-18cc-2fadfc8c9716@linux.intel.com> (raw)
In-Reply-To: <153857020163.28435.6344999604040734702@skylake-alporthouse-com>


On 03/10/2018 13:36, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-10-03 13:03:53)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> A collection of patches which I have been sending before, sometimes together and
>> sometimes separately, which enable intel_gpu_top to report queue depths (also
>> translates as overall GPU load average) and per DRM client per engine busyness.
> 
> Queued falls apart with v.engine and I don't have a good suggestion for
> a remedy. :(

Indeed, I forgot about it. I have now even found a few months old branch 
with queued and runnable removed already.

I think we also talked about the option of exposing aggregate engine 
class counters but that also has problems.

We could go global and not expose this per engine, but that wouldn't 
make <gen11 users happy.

Regards,

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

  reply	other threads:[~2018-10-03 12:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 12:03 [RFC 00/13] 21st century intel_gpu_top Tvrtko Ursulin
2018-10-03 12:03 ` [RFC 01/13] drm/i915/pmu: Fix enable count array size and bounds checking Tvrtko Ursulin
2018-10-03 12:03 ` [RFC 02/13] drm/i915: Keep a count of requests waiting for a slot on GPU Tvrtko Ursulin
2018-10-03 12:03 ` [RFC 03/13] drm/i915: Keep a count of requests submitted from userspace Tvrtko Ursulin
2018-10-03 12:03 ` [RFC 04/13] drm/i915/pmu: Add queued counter Tvrtko Ursulin
2018-10-03 12:03 ` [RFC 05/13] drm/i915/pmu: Add runnable counter Tvrtko Ursulin
2018-10-03 12:03 ` [RFC 06/13] drm/i915/pmu: Add running counter Tvrtko Ursulin
2018-10-03 12:04 ` [RFC 07/13] drm/i915: Store engine backpointer in the intel_context Tvrtko Ursulin
2018-10-03 12:04 ` [RFC 08/13] drm/i915: Move intel_engine_context_in/out into intel_lrc.c Tvrtko Ursulin
2018-10-03 12:04 ` [RFC 09/13] drm/i915: Track per-context engine busyness Tvrtko Ursulin
2018-10-03 12:04 ` [RFC 10/13] drm/i915: Expose list of clients in sysfs Tvrtko Ursulin
2018-10-03 12:04 ` [RFC 11/13] drm/i915: Update client name on context create Tvrtko Ursulin
2018-10-03 12:04 ` [RFC 12/13] drm/i915: Expose per-engine client busyness Tvrtko Ursulin
2018-10-03 12:04 ` [RFC 13/13] drm/i915: Add sysfs toggle to enable per-client engine stats Tvrtko Ursulin
2018-10-03 12:36 ` [RFC 00/13] 21st century intel_gpu_top Chris Wilson
2018-10-03 12:57   ` Tvrtko Ursulin [this message]
2018-10-03 14:38 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-10-10 11:49 ` [RFC 00/13] " 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=8de45bc3-00f6-892b-18cc-2fadfc8c9716@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=tursulin@ursulin.net \
    /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.