From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t 4/4] intel_gpu_top: Aggregate engine classes in all output modes
Date: Thu, 26 Jan 2023 16:12:32 +0000 [thread overview]
Message-ID: <b624ed98-0cbe-677c-23a8-bd06882eaad2@linux.intel.com> (raw)
In-Reply-To: <20230126155017.hx37o7gmvolcah5p@kamilkon-desk1>
On 26/01/2023 15:50, Kamil Konieczny wrote:
> On 2023-01-12 at 17:47:30 +0000, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Use the same default for stdout and JSON output modes as it is for
>> interactive.
>>
>> Previously added command line switch can be used to go back to showing all
>> physical engines.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
>
> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Downside with this one is that the default output for -l and -J modes
will change. Which may result in bug reports. I am undecided on
balance.. should have tagged it as RFC really. Thoughts?
Regards,
Tvrtko
>> ---
>> tools/intel_gpu_top.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/intel_gpu_top.c b/tools/intel_gpu_top.c
>> index e91b47baf72b..7aa233570463 100644
>> --- a/tools/intel_gpu_top.c
>> +++ b/tools/intel_gpu_top.c
>> @@ -2509,11 +2509,12 @@ int main(int argc, char **argv)
>> if (signal(SIGINT, sigint_handler) == SIG_ERR)
>> fprintf(stderr, "Failed to install signal handler!\n");
>>
>> + class_view = !physical_engines;
>> +
>> switch (output_mode) {
>> case INTERACTIVE:
>> pops = &term_pops;
>> interactive_stdin();
>> - class_view = !physical_engines;
>> break;
>> case STDOUT:
>> pops = &stdout_pops;
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2023-01-26 16:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 17:47 [igt-dev] [PATCH i-g-t 0/4] Some intel_gpu_top tweaks Tvrtko Ursulin
2023-01-12 17:47 ` [igt-dev] [PATCH i-g-t 1/4] intel_gpu_top: Fix man page formatting Tvrtko Ursulin
2023-01-26 15:39 ` Kamil Konieczny
2023-01-26 16:09 ` Tvrtko Ursulin
2023-01-26 17:08 ` Kamil Konieczny
2023-01-12 17:47 ` [igt-dev] [PATCH i-g-t 2/4] intel_gpu_top: Automatically enclose JSON output into brackets Tvrtko Ursulin
2023-01-26 15:41 ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-01-26 16:10 ` Tvrtko Ursulin
2023-01-12 17:47 ` [igt-dev] [PATCH i-g-t 3/4] intel_gpu_top: Add command line switch to start in physical engine mode Tvrtko Ursulin
2023-01-26 15:48 ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-01-12 17:47 ` [igt-dev] [PATCH i-g-t 4/4] intel_gpu_top: Aggregate engine classes in all output modes Tvrtko Ursulin
2023-01-26 15:50 ` [igt-dev] [Intel-gfx] " Kamil Konieczny
2023-01-26 16:12 ` Tvrtko Ursulin [this message]
2023-01-12 18:34 ` [igt-dev] ✓ Fi.CI.BAT: success for Some intel_gpu_top tweaks Patchwork
2023-01-13 7:47 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-01-26 15:53 ` [igt-dev] [Intel-gfx] [PATCH i-g-t 0/4] " Kamil Konieczny
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=b624ed98-0cbe-677c-23a8-bd06882eaad2@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=dmitry.v.rogozhkin@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--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