Bug 108689

Summary: new version of intel_gpu_top lost option of output log to stdio or file
Product: DRI Reporter: Alex <3.14pi>
Component: IGTAssignee: Tvrtko Ursulin <tvrtko.ursulin>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: low CC: intel-gfx-bugs, tvrtko.ursulin
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard: ReadyForDev
i915 platform: i915 features:

Description Alex 2018-11-07 13:14:46 UTC
Old version 1.22 of intel_gpu_top has option to output usage statistic to file or stdio, but new v1.23 lost this option.

This needed for monitoring GPU usage on server and send data to web page via socket.io.

Also, will be cool if intel_gpu_top can output stats to stdio in JSON format!
Thanks.
Comment 1 Tvrtko Ursulin 2018-11-08 09:13:39 UTC
Hi,

Two questions:

New intel_gpu_top also supports a pretty different set of data. So if we added this option - can you adapt to the new data and is it useful for your use case?

Secondly, you could get the CSV data for all the stuff new intel_gpu_top shows in a bit more raw form from the standard kernel perf tool. Just one example on render command streamer busyness:

   perf stat -a -e i915/rcs0-busy/ -I 1000 -x

As said, all the data new version shows is available like this, albeit with some required post-procesing like converting absolute time differences to percentages and similar.
Comment 2 Alex 2018-11-08 12:28:34 UTC
1) Yes, can adapt without any problem. I my case I need render usage and video encode/decode usage data, and memory usage speed/capacity.

2)I know, but this is required extra step to convert/represent data in percent and custom parser. Will be cool if intel_gpu_top just print to stdio raw JSON.
Comment 3 Alex 2018-11-30 16:05:36 UTC
Any news?
Comment 4 Tvrtko Ursulin 2018-12-03 09:25:21 UTC
Sorry it slipped from my radar. We could add some form of non-interactive stdio output I guess, shouldn't be too difficult. Will see how it fits against the higher priority work.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.