From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Rob Clark <robdclark@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: "Intel Graphics Development" <Intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Christian König" <christian.koenig@amd.com>,
"Chris Healy" <cphealy@gmail.com>,
"David M Nieto" <David.Nieto@amd.com>
Subject: Re: [Intel-gfx] [PATCH 6/7] drm: Document fdinfo format specification
Date: Mon, 21 Feb 2022 11:14:33 +0000 [thread overview]
Message-ID: <c00c7999-79d1-7c3e-d4e8-df2a887834d8@linux.intel.com> (raw)
In-Reply-To: <fb6f1a2c-6e23-cfdf-2ce5-80209a005227@linux.intel.com>
Hi Rob,
On 25/01/2022 10:24, Tvrtko Ursulin wrote:
>
> On 21/01/2022 11:50, Tvrtko Ursulin wrote:
>> On 20/01/2022 16:44, Rob Clark wrote:
>
> [snip]
>
>>> If there is a tool somewhere that displays this info, that would be
>>> useful for testing my implementation.
>>
>> I have a patch to Intel specific intel_gpu_top (see
>> https://patchwork.freedesktop.org/patch/468491/?series=98555&rev=1).
>> I'll have a look to see how much work would it be to extract common
>> bits into a library and write a quick agnostic tool using it.
>
> I factored out some code from intel_gpu_top in a quick and dirty attempt
> to make it generic and made a very rudimentary tools/gputop:
>
> https://cgit.freedesktop.org/~tursulin/intel-gpu-tools/log/?h=gputop
Have you managed to spend any time playing with this yet?
The only remaining open was Daniel's mild concern if vendor agnostic
userspace is possible using the proposed spec. If you managed to wire up
the compliant exports and gputop tool works I think that concern would
be settled.
Regards,
Tvrtko
WARNING: multiple messages have this Message-ID (diff)
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Rob Clark <robdclark@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: "Intel Graphics Development" <Intel-gfx@lists.freedesktop.org>,
"Daniel Stone" <daniel@fooishbar.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Christian König" <christian.koenig@amd.com>,
"Chris Healy" <cphealy@gmail.com>,
"David M Nieto" <David.Nieto@amd.com>
Subject: Re: [Intel-gfx] [PATCH 6/7] drm: Document fdinfo format specification
Date: Mon, 21 Feb 2022 11:14:33 +0000 [thread overview]
Message-ID: <c00c7999-79d1-7c3e-d4e8-df2a887834d8@linux.intel.com> (raw)
In-Reply-To: <fb6f1a2c-6e23-cfdf-2ce5-80209a005227@linux.intel.com>
Hi Rob,
On 25/01/2022 10:24, Tvrtko Ursulin wrote:
>
> On 21/01/2022 11:50, Tvrtko Ursulin wrote:
>> On 20/01/2022 16:44, Rob Clark wrote:
>
> [snip]
>
>>> If there is a tool somewhere that displays this info, that would be
>>> useful for testing my implementation.
>>
>> I have a patch to Intel specific intel_gpu_top (see
>> https://patchwork.freedesktop.org/patch/468491/?series=98555&rev=1).
>> I'll have a look to see how much work would it be to extract common
>> bits into a library and write a quick agnostic tool using it.
>
> I factored out some code from intel_gpu_top in a quick and dirty attempt
> to make it generic and made a very rudimentary tools/gputop:
>
> https://cgit.freedesktop.org/~tursulin/intel-gpu-tools/log/?h=gputop
Have you managed to spend any time playing with this yet?
The only remaining open was Daniel's mild concern if vendor agnostic
userspace is possible using the proposed spec. If you managed to wire up
the compliant exports and gputop tool works I think that concern would
be settled.
Regards,
Tvrtko
next prev parent reply other threads:[~2022-02-21 11:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 16:55 [PATCH 0/7] Per client GPU stats Tvrtko Ursulin
2022-01-06 16:55 ` [Intel-gfx] " Tvrtko Ursulin
2022-01-06 16:55 ` [PATCH 1/7] drm/i915: Explicitly track DRM clients Tvrtko Ursulin
2022-01-06 16:55 ` [Intel-gfx] " Tvrtko Ursulin
2022-01-06 16:55 ` [PATCH 2/7] drm/i915: Make GEM contexts " Tvrtko Ursulin
2022-01-06 16:55 ` [Intel-gfx] " Tvrtko Ursulin
2022-01-06 16:55 ` [PATCH 3/7] drm/i915: Track runtime spent in closed and unreachable GEM contexts Tvrtko Ursulin
2022-01-06 16:55 ` [Intel-gfx] " Tvrtko Ursulin
2022-01-06 16:55 ` [PATCH 4/7] drm/i915: Track all user contexts per client Tvrtko Ursulin
2022-01-06 16:55 ` [Intel-gfx] " Tvrtko Ursulin
2022-01-06 16:55 ` [PATCH 5/7] drm/i915: Track context current active time Tvrtko Ursulin
2022-01-06 16:55 ` [Intel-gfx] " Tvrtko Ursulin
2022-01-06 16:55 ` [PATCH 6/7] drm: Document fdinfo format specification Tvrtko Ursulin
2022-01-06 16:55 ` [Intel-gfx] " Tvrtko Ursulin
2022-01-19 15:08 ` Daniel Vetter
2022-01-19 15:08 ` [Intel-gfx] " Daniel Vetter
2022-01-20 10:30 ` Tvrtko Ursulin
2022-01-20 10:30 ` [Intel-gfx] " Tvrtko Ursulin
2022-01-20 16:44 ` Rob Clark
2022-01-20 16:44 ` Rob Clark
2022-01-21 11:50 ` Tvrtko Ursulin
2022-01-21 11:50 ` Tvrtko Ursulin
2022-01-25 10:24 ` Tvrtko Ursulin
2022-01-25 10:24 ` Tvrtko Ursulin
2022-01-25 10:36 ` Christian König
2022-01-25 10:36 ` Christian König
2022-02-21 11:14 ` Tvrtko Ursulin [this message]
2022-02-21 11:14 ` Tvrtko Ursulin
2022-01-06 16:55 ` [PATCH 7/7] drm/i915: Expose client engine utilisation via fdinfo Tvrtko Ursulin
2022-01-06 16:55 ` [Intel-gfx] " Tvrtko Ursulin
2022-02-19 0:51 ` Umesh Nerlige Ramappa
2022-02-19 0:51 ` [Intel-gfx] " Umesh Nerlige Ramappa
2022-02-22 12:31 ` Tvrtko Ursulin
2022-02-22 12:31 ` [Intel-gfx] " Tvrtko Ursulin
2022-01-06 18:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Per client GPU stats (rev6) Patchwork
2022-01-06 18:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-06 18:20 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-01-06 18:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-07 14:46 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 15:49 [PATCH 0/7] Per client GPU stats Tvrtko Ursulin
2021-12-03 15:49 ` [Intel-gfx] [PATCH 6/7] drm: Document fdinfo format specification Tvrtko Ursulin
2021-09-22 15:51 [PATCH 0/7] Per client GPU stats Tvrtko Ursulin
2021-09-22 15:51 ` [Intel-gfx] [PATCH 6/7] drm: Document fdinfo format specification 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=c00c7999-79d1-7c3e-d4e8-df2a887834d8@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=David.Nieto@amd.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=cphealy@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@gmail.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.