Since it seemed like a re-occurring complaint that developers didn't feel they could trust the numbers from intel-gpu-top I reviewed the implementation and came across a few issues that I've tried to address in this series. Just to let others know; I'm also experimenting with the possibility of collecting this data, and more, from the kernel via the perf interface (building on work originally done by Chris Wilson last year) so these may just be stop-gap improvements if those experiments pan out. - Robert Robert Bragg (9): intel_gpu_top: don't fclose NULL output intel_gpu_top: aim for 2000 samples per frame intel_gpu_top: ignore out of range ring pointers intel_gpu_top: read max/current gt freq via sysfs intel_reg: rename RING_LEN RING_CTL intel_reg: add RING_CCID current context ID reg instdone: Add human readable names for HSW intel_gpu_top: account for per context statistics intel_gpu_top: hide absolute counter values lib/instdone.c | 28 +-- lib/intel_reg.h | 8 +- tools/intel_gpu_top.c | 519 ++++++++++++++++++++++++++++++++++---------------- 3 files changed, 368 insertions(+), 187 deletions(-) -- 2.0.1 --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
