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>,
Eero Tamminen <eero.t.tamminen@intel.com>
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t 2/4] intel_gpu_top: Automatically enclose JSON output into brackets
Date: Thu, 26 Jan 2023 16:10:37 +0000 [thread overview]
Message-ID: <ec09497f-f3fb-a34b-d6a4-c9763a7ba385@linux.intel.com> (raw)
In-Reply-To: <20230126154124.hlcokp3b62d3ncvv@kamilkon-desk1>
On 26/01/2023 15:41, Kamil Konieczny wrote:
> On 2023-01-12 at 17:47:28 +0000, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Parsers need the whole output enclosed into square brackets so every
>> period sample becomes an array element.
>>
>> So far we have been suggesting this in the man page but we can trivially
>> make the tool output that itself.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Eero Tamminen <eero.t.tamminen@intel.com>
>
> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Disclaimer with this one is that I am not really sure if it is a good
idea. How people might use the JSON output and if this helps or harms
them I mean, I have no idea.
Regards,
Tvrtko
>> ---
>> man/intel_gpu_top.rst | 2 +-
>> tools/intel_gpu_top.c | 6 ++++++
>> 2 files changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/man/intel_gpu_top.rst b/man/intel_gpu_top.rst
>> index b0c95446a011..3317e04816b4 100644
>> --- a/man/intel_gpu_top.rst
>> +++ b/man/intel_gpu_top.rst
>> @@ -85,7 +85,7 @@ Filter types: ::
>> JSON OUTPUT
>> ===========
>>
>> -To parse the JSON as output by the tool the consumer should wrap its entirety into square brackets ([ ]). This will make each sample point a JSON array element and will avoid "Multiple root elements" JSON validation error.
>> +JSON output will be correctly terminated when the tool cleanly exits, otherwise one square bracket needs to be added before parsing.
>>
>> LIMITATIONS
>> ===========
>> diff --git a/tools/intel_gpu_top.c b/tools/intel_gpu_top.c
>> index 6de8a164fcff..c4d98de4fe31 100644
>> --- a/tools/intel_gpu_top.c
>> +++ b/tools/intel_gpu_top.c
>> @@ -2597,6 +2597,9 @@ int main(int argc, char **argv)
>> scan_clients(clients, false);
>> codename = igt_device_get_pretty_name(&card, false);
>>
>> + if (output_mode == JSON)
>> + printf("[\n");
>> +
>> while (!stop_top) {
>> struct clients *disp_clients;
>> bool consumed = false;
>> @@ -2683,6 +2686,9 @@ int main(int argc, char **argv)
>> usleep(period_us);
>> }
>>
>> + if (output_mode == JSON)
>> + printf("]\n");
>> +
>> if (clients)
>> free_clients(clients);
>>
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2023-01-26 16:10 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 [this message]
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
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=ec09497f-f3fb-a34b-d6a4-c9763a7ba385@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=eero.t.tamminen@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