This reads the GPU's performance counters via MI_REPORT_PERF_COUNT and
prints them in a top-style interface. While it can be useful in and of
itself, it also documents the performance counters and lets us verify
that they're working.
Currently, it only supports Ironlake.
v2 [Ken]: Rebase on master and fix compilation failures; make it abort
on non-Ironlake platforms to avoid GPU hangs; rename from 'chaps' to
intel_perf_counters since that acronym isn't used any longer; write the
above commit message.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
It may sometimes be undesirable to build or install the quick dumper.
This was requested by Damien.
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
This isn't strictly necessary it would have been easy enough to simply
convert intel_chipset.h but this should be nice prep work for directly
doing MMIO. It also serves as a nice review point.
It's demonstrated with an autodetect function in the script. That
autodetect has a hardcoded path that shouldn't be there, but it will go
away in the next patch when we can properly link in libpciaccess.
Thanks to Matt for helping whip the automake stuff into shape.
v2: Switch to $(top_srcdir)
Reviewed-by: Matt Turner <mattst88@gmail.com>
Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
This is the base tool for quick dump. At it's heart, quick dump is
simply a basic text parsing thingie which plugs into intel-gpu-tools to
do something similar to intel_reg_dumper.
The format for the register definition files is very open, so it's just
something simple for now.
Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
In Valleyview the DPLL and lane control registers are accessible only
through side band fabric called DPIO. Added two tools to read and write
registers residing in this space.
v2: Moved the core read/write functions to lib/intel_dpio.c based on
Ben's feedback
Signed-off-by: Vijay Purushothaman <vijay.a.purushothaman@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
We should get more kms tests soon, and not needing to copy-paste a
nice test pattern should be useful.
That establishes a firm depency of i-g-t on cairo over everything, but
I don't care so much about that.
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
This is a command-line tool that allows us to display and modify the
InfoFrames we send.
v2: use argv instead of stdin
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
The tool allows you to change the panel fitter settings, so you can
change the size of the screen being displayed on your monitor without
changing the real pixel size of your desktop. The biggest use case for
this tool is to work around overscan done by TVs and some monitors in
interlaced mode.
v2: reviews by Ben, Chris and Rodrigo
- don't install
- use intel_register_access_init
- check for maximum X and Y values
- add a disclaimer saying this is not the real solution
- print less when pf is disabled and option '-l' is used
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Headers are found under top_srcdir/
Headers are CPP flags, not C Flags
libintel_tools.la is located in top_builddir.
Use dist_bin_SCRIPTS so it is included in tarball
Line-up the line continuation characters
Acked-by: Ben Widawsky <ben@bwidawsk.net>
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
Use CWARNFLAGS as in all of xorg. There seems to be no reason why this
module should be different. The warnings were updated recently
for those who install the latest util-macros.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
The goal of this tool is to be usable as a test for whether something
(suspend/resume, GPU reset, bugs, whatever) may have lost various
required hardware setup specified in the docs.
Reviewed-By: Eugeni Dodonov <eugeni.dodonov@intel.com>
This app is required for debug features which seem to (undocumented)
reset themselves if/when the GT goes to sleep.
It is also useful for those doing general debugging or profiling from
userspace when they do not wish to have the GT sleep.
v2: made forcewaked more daemon-like
Cc: Chris Wilson <chris@chris-wilson.co.uk>
It has been supersede by intel_error_decode for the user-facing role of
obtaining debug info after a crash.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
This is something I sometimes want to do in testing, to see if a
mystery bug (say, 29172) is due to broken clock gating. Sadly, in
this case it isn't. Note that it isn't supported on non-ILK chipsets
yet.
Rather than add yet another decoder into the drivers, I rather just emit
a binary blob and use the decoder being developed here.
As it is a pure debugging feature, lets not package it.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
This is a handy tool to just check state of one register, which might
not bother to be included in intel_reg_dumper tool. And also take in Ben's
original full range register dump with '-f' option.
Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Introduce a second decoder that simpler operates on a file so that it
can be run on dumped batchbuffers independent of the gpu.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
A simple variant on time crossed with intel_gpu_top to estimate the
amount of GPU activity during a program's execution time.
The resource usage (sys+user, i.e. CPU %) is for the child, but the
GPU measure is global. Hmm.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Right now it requires a filename on the command line, (such as
/debug/dri/0/i915_batchbuffers). We plan to make it smarter in
the future by going out and collecting all the data it needs.
