Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org, Intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [RFC 1/3] intel_gpu_top: User friendly device listing
Date: Tue, 10 Nov 2020 11:52:50 +0000	[thread overview]
Message-ID: <8edab1c5-6f7b-5cae-3bda-5288e6bd64fe@linux.intel.com> (raw)
In-Reply-To: <20201110114602.GG5736@zkempczy-mobl2>


On 10/11/2020 11:46, Zbigniew Kempczyński wrote:

[snip]

>>>> diff --git a/tools/intel_gpu_top.c b/tools/intel_gpu_top.c
>>>> index 298defa4e6ed..5230472d2af4 100644
>>>> --- a/tools/intel_gpu_top.c
>>>> +++ b/tools/intel_gpu_top.c
>>>> @@ -1313,7 +1313,6 @@ int main(int argc, char **argv)
>>>>    	unsigned int i;
>>>>    	int ret = 0, ch;
>>>>    	bool list_device = false;
>>>> -	enum igt_devices_print_type printtype = IGT_PRINT_SIMPLE;
>>>>    	char *pmu_device, *opt_device = NULL;
>>>>    	struct igt_device_card card;
>>>> @@ -1388,7 +1387,7 @@ int main(int argc, char **argv)
>>>>    	igt_devices_scan(false);
>>>>    	if (list_device) {
>>>> -		igt_devices_print(printtype);
>>>> +		igt_devices_print(IGT_PRINT_USER);
>>>
>>> I would add at least possibility to use simple view to suggest
>>> how to use pci/sys filter. With USER print format we see only
>>
>> You mean the blurb printed out by igt_device_print_filter_types (currently
>> printed as part of help text) or something else?
> 
> Yes. We know lsgpu and intel_gpu_top selection is same and you're
> also printing filter syntax on 'intel_gpu_top -h'. But without
> using 'lsgpu -s' you won't guess how to specify sys:... filter.

My thinking is that typical intel_gpu_top user wouldn't want/need to 
concern themselves with different filters but just copy&paste what was 
listed from intel_gpu_top -L. In which case..

>>
>>> drm paths. But I won't insist for that, using drm selection
>>> is ok for me.
>>
>> Good point actually, intel_gpu_top should probably default to "--pci"
>> listing type since it monitors GPUs with no notion of DRM master/render.
>>
>>> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
>>
>> Thanks! Let me know if you agree with "--pci" by default for intel_gpu_top
>> and if it is okay to keep the r-b?
> 
> If it is not problem you could provide --pci and --sysfs too to be compliant
> with lsgpu switches. But there are minor nits and you can keep r-b with
> the code as it is.

... I did not see the value of supporting --drm/--pci/--sysfs from 
intel_gpu_top.

So "--pci" by default should "JustWork" and make end users happy. As 
long as the help text is clear enough what needs to be copy&pasted, 
which may need improvement. If I am not missing something else.

Regards,

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

  reply	other threads:[~2020-11-10 11:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 10:48 [Intel-gfx] [RFC 0/3] User friendly lsgpu default output Tvrtko Ursulin
2020-11-09 10:48 ` [Intel-gfx] [RFC 1/3] intel_gpu_top: User friendly device listing Tvrtko Ursulin
2020-11-10 11:13   ` Zbigniew Kempczyński
2020-11-10 11:19     ` Tvrtko Ursulin
2020-11-10 11:46       ` Zbigniew Kempczyński
2020-11-10 11:52         ` Tvrtko Ursulin [this message]
2020-11-10 12:27           ` Zbigniew Kempczyński
2020-11-09 10:48 ` [Intel-gfx] [RFC 2/3] lsgpu: " Tvrtko Ursulin
2020-11-10 11:03   ` Zbigniew Kempczyński
2020-11-10 11:20     ` Tvrtko Ursulin
2020-11-10 11:35       ` Zbigniew Kempczyński
2020-11-09 10:48 ` [Intel-gfx] [RFC 3/3] lsgpu: Add filter type print-out selection Tvrtko Ursulin
2020-11-10 11:02   ` Zbigniew Kempczyński
2020-11-09 11:21 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for User friendly lsgpu default output 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=8edab1c5-6f7b-5cae-3bda-5288e6bd64fe@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=zbigniew.kempczynski@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