public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Rob Clark <robdclark@chromium.org>
Cc: "Tvrtko Ursulin" <tvrtko.ursulin@intel.com>,
	"Christian König" <ckoenig.leichtzumerken@gmail.com>,
	Intel-gfx@lists.freedesktop.org, igt-dev@lists.freedesktop.org,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [igt-dev] [PATCH i-g-t 8/8] gputop: Basic vendor agnostic GPU top tool
Date: Mon, 15 May 2023 12:10:43 +0100	[thread overview]
Message-ID: <e94c4470-d9b1-19db-9948-3d8caaf8b7b8@linux.intel.com> (raw)
In-Reply-To: <CAJs_Fx7=zKUeE5sejc-ZCjUZ47W6Taw4_AP9ZWT7e-kkzL3h2g@mail.gmail.com>


On 12/05/2023 15:18, Rob Clark wrote:
> On Thu, Apr 6, 2023 at 7:33 AM Tvrtko Ursulin
> <tvrtko.ursulin@linux.intel.com> wrote:
>>
>>
>> On 06/04/2023 15:21, Rob Clark wrote:
>>> On Thu, Apr 6, 2023 at 4:08 AM Tvrtko Ursulin
>>> <tvrtko.ursulin@linux.intel.com> wrote:
>>>>
>>>>
>>>> On 05/04/2023 18:57, Rob Clark wrote:
>>>>> On Tue, Jan 31, 2023 at 3:33 AM Tvrtko Ursulin
>>>>> <tvrtko.ursulin@linux.intel.com> wrote:
>>>>>>
>>>>>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>>>>>
>>>>>> Rudimentary vendor agnostic example of how lib_igt_drm_clients can be used
>>>>>> to display a sorted by card and usage list of processes using GPUs.
>>>>>>
>>>>>> Borrows a bit of code from intel_gpu_top but for now omits the fancy
>>>>>> features like interactive functionality, card selection, client
>>>>>> aggregation, sort modes, JSON output  and pretty engine names. Also no
>>>>>> support for global GPU or system metrics.
>>>>>>
>>>>>> On the other hand it shows clients from all DRM cards which
>>>>>> intel_gpu_top does not do.
>>>>>>
>>>>>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>>>>> Cc: Rob Clark <robdclark@chromium.org>
>>>>>> Cc: Christian König <ckoenig.leichtzumerken@gmail.com>
>>>>>> Acked-by: Christian König <christian.koenig@amd.com>
>>>>>
>>>>> Reviewed-by: Rob Clark <robdclark@chromium.org>
>>>>
>>>> Presumably for 8/8 only?
>>>>
>>>> The rest of the series does not apply any more by now. I need to rebase..
>>>
>>> I didn't look closely at the rest of the series (was kinda assuming
>>> that was mostly just moving things around).. but I see you rebased it
>>> so I can take a look.
>>
>> There's a lot in there - first patch is extracting some code into a
>> library, with the corresponding renames, but then there are six patches
>> of tweaks and feature additions which finally make gputop possible.
>>
>> Hopefully you can penetrate the concepts. It was all at least Valgrind
>> clean back in the day I first did it.
>>
> 
> by now I've read (and rebased locally) the series, and even added a
> couple things on top.. so r-b for the series, we should get this
> landed

Thanks for the reviews, pushed!

Lets see if the future holds for this small tool.

Regards,

Tvrtko

  reply	other threads:[~2023-05-15 11:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 11:32 [igt-dev] [PATCH i-g-t v3 0/8] Vendor agnostic gputop Tvrtko Ursulin
2023-01-31 11:32 ` [igt-dev] [PATCH i-g-t 1/8] lib: Extract igt_drm_clients from intel_gpu_top Tvrtko Ursulin
2023-01-31 11:32 ` [igt-dev] [PATCH i-g-t 2/8] lib: Allow specifying custom engine map Tvrtko Ursulin
2023-01-31 11:32 ` [igt-dev] [PATCH i-g-t 3/8] lib/igt_drm_clients: Record client drm minor Tvrtko Ursulin
2023-01-31 11:32 ` [igt-dev] [PATCH i-g-t 4/8] lib/igt_drm_clients: Support multiple DRM cards Tvrtko Ursulin
2023-01-31 11:32 ` [igt-dev] [PATCH i-g-t 5/8] lib/igt_drm_fdinfo: Track largest engine index Tvrtko Ursulin
2023-01-31 11:32 ` [igt-dev] [PATCH i-g-t 6/8] lib/igt_drm_clients: Decouple hardcoded engine assumptions Tvrtko Ursulin
2023-01-31 11:32 ` [igt-dev] [PATCH i-g-t 7/8] lib/igt_drm_clients: Enforce client status sort order in the library Tvrtko Ursulin
2023-01-31 11:32 ` [igt-dev] [PATCH i-g-t 8/8] gputop: Basic vendor agnostic GPU top tool Tvrtko Ursulin
2023-02-03 16:42   ` Kamil Konieczny
2023-02-06  9:19     ` Tvrtko Ursulin
2023-02-06 14:04       ` Kamil Konieczny
2023-04-05 17:57   ` Rob Clark
2023-04-06 11:08     ` Tvrtko Ursulin
2023-04-06 14:21       ` Rob Clark
2023-04-06 14:31         ` Tvrtko Ursulin
2023-05-12 14:18           ` Rob Clark
2023-05-15 11:10             ` Tvrtko Ursulin [this message]
2023-01-31 12:14 ` [igt-dev] ✓ Fi.CI.BAT: success for Vendor agnostic gputop (rev5) Patchwork
2023-01-31 15:55 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-04-17 10:57 [igt-dev] [PATCH i-g-t v5 0/8] Vendor agnostic gputop Tvrtko Ursulin
2023-04-17 10:57 ` [igt-dev] [PATCH i-g-t 8/8] gputop: Basic vendor agnostic GPU top tool Tvrtko Ursulin
2023-04-06 14:15 [igt-dev] [PATCH i-g-t v4 0/8] Vendor agnostic gputop Tvrtko Ursulin
2023-04-06 14:15 ` [igt-dev] [PATCH i-g-t 8/8] gputop: Basic vendor agnostic GPU top tool Tvrtko Ursulin
2022-11-11 15:58 [igt-dev] [PATCH i-g-t 0/8] Vendor agnostic gputop Tvrtko Ursulin
2022-11-11 15:58 ` [igt-dev] [PATCH i-g-t 8/8] gputop: Basic vendor agnostic GPU top tool Tvrtko Ursulin
2022-11-16 13:43   ` Philipp Zabel
2022-06-16 14:06 [igt-dev] [PATCH i-g-t 0/8] Vendor agnostic gputop Tvrtko Ursulin
2022-06-16 14:06 ` [igt-dev] [PATCH i-g-t 8/8] gputop: Basic vendor agnostic GPU top tool Tvrtko Ursulin
2022-06-17  7:20   ` Christian König
2022-06-17 10:09     ` Tvrtko Ursulin
2022-06-17 11:33       ` Christian König
2022-05-11 12:18 [igt-dev] [PATCH i-g-t 0/8] Vendor agnostic gputop Tvrtko Ursulin
2022-05-11 12:18 ` [igt-dev] [PATCH i-g-t 8/8] gputop: Basic vendor agnostic GPU top tool Tvrtko Ursulin
2022-05-11 14:42   ` Christian König
2022-05-11 15:07     ` Tvrtko Ursulin
2022-04-05  8:41 [igt-dev] [PATCH i-g-t 0/8] Vendor agnostic gputop Tvrtko Ursulin
2022-04-05  8:41 ` [igt-dev] [PATCH i-g-t 8/8] gputop: Basic vendor agnostic GPU top tool 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=e94c4470-d9b1-19db-9948-3d8caaf8b7b8@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=robdclark@chromium.org \
    --cc=tvrtko.ursulin@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