Intel-GFX Archive on 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
Subject: Re: [Intel-gfx] [PATCH 0/5] Per client engine busyness
Date: Mon, 16 Dec 2019 13:20:25 +0000	[thread overview]
Message-ID: <a52bb35b-cfe2-8a82-ba23-485ee0e49488@linux.intel.com> (raw)
In-Reply-To: <157650175177.2428.17602949228966194239@skylake-alporthouse-com>


On 16/12/2019 13:09, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-12-16 12:06:59)
>> Implementation wise we add a a bunch of files in sysfs like:
>>
>>          # cd /sys/class/drm/card0/clients/
>>          # tree
>>          .
>>          ├── 7
>>          │   ├── busy
>>          │   │   ├── 0
> 
> Prefer '0' over rcs?

I think so, saves userspace keeping a map of names to class enum. Or 
maybe it doesn't, depends. Saves us having to come up with ABI names. 
But I think I could be easily convinced either way.

>> I will post the corresponding patch to intel_gpu_top for reference as well.
> 
> The other requirement is that we need to at least prove the sysfs
> interface exists in gt. perf_sysfs?
> 
> Quick list,
> - check igt_spin_t responses (pretty much verbatim of perf_pmu.c)
> - check the client name is correct around fd passing
> - check interactions with ctx->engines[]

Yep, I know it will be needed. But haven't been bothering yet since the 
series has been in a hopeless mode for what, two years or so. I forgot 
to name it RFC this time round.. :)

Regards,

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

  reply	other threads:[~2019-12-16 13:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 12:06 [Intel-gfx] [PATCH 0/5] Per client engine busyness Tvrtko Ursulin
2019-12-16 12:07 ` [Intel-gfx] [PATCH 1/5] drm/i915: Track per-context " Tvrtko Ursulin
2019-12-16 12:40   ` Chris Wilson
2019-12-16 13:09     ` Tvrtko Ursulin
2020-01-30 18:05       ` Tvrtko Ursulin
2020-01-30 21:42         ` Chris Wilson
2019-12-16 12:07 ` [Intel-gfx] [PATCH 2/5] drm/i915: Expose list of clients in sysfs Tvrtko Ursulin
2019-12-16 12:51   ` Chris Wilson
2019-12-16 18:34     ` Tvrtko Ursulin
2019-12-16 12:53   ` Chris Wilson
2019-12-16 13:13     ` Tvrtko Ursulin
2019-12-17 17:21     ` Tvrtko Ursulin
2019-12-17 17:26       ` Chris Wilson
2019-12-16 12:55   ` Chris Wilson
2019-12-16 13:16     ` Tvrtko Ursulin
2019-12-16 13:17   ` Chris Wilson
2019-12-16 13:28     ` Tvrtko Ursulin
2019-12-16 13:41       ` Chris Wilson
2019-12-16 12:07 ` [Intel-gfx] [PATCH 3/5] drm/i915: Update client name on context create Tvrtko Ursulin
2019-12-16 12:57   ` Chris Wilson
2019-12-16 12:07 ` [Intel-gfx] [PATCH 4/5] drm/i915: Expose per-engine client busyness Tvrtko Ursulin
2019-12-16 12:07 ` [Intel-gfx] [PATCH 5/5] drm/i915: Add sysfs toggle to enable per-client engine stats Tvrtko Ursulin
2019-12-16 13:09 ` [Intel-gfx] [PATCH 0/5] Per client engine busyness Chris Wilson
2019-12-16 13:20   ` Tvrtko Ursulin [this message]
2019-12-16 17:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-12-16 17:58 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=a52bb35b-cfe2-8a82-ba23-485ee0e49488@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    /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