mirror of
https://github.com/varun-r-mallya/sysprof.git
synced 2025-12-31 20:36:25 +00:00
94bb2fba0d
This reveals that we've got really bogus times from these events. I think there are two things here: the begin is the submit time, not the submit-to-hardware time. And the end time is retire, which is too delayed to be really useful. We need to move i915 over to the low-level tracepoints. However, this code proved to be useful for vc4, where I have good timings.
Sysprof is a sampling profiler that uses a kernel module to generate
stacktraces which are then interpreted by the userspace program
"sysprof".
See the Sysprof homepage:
http://sysprof.com/
for more information
Questions, patches and bug reports should be sent to the sysprof
mailing list:
sysprof-list@gnome.org
The list is archived here:
https://mail.gnome.org/archives/sysprof-list/
Debugging symbols
- The programs and libraries you want to profile should be compiled
with -fno-omit-frame-pointer and have debugging symbols available,
or you won't get much usable information.
Building Sysprof
----------------
You need some packages installed. The package names may vary depending on your
distribution, the following command works on Fedora 25:
sudo dnf install gcc gcc-c++ ninja-build gtk3-devel
Then do the following:
meson --prefix=/usr build
cd build
ninja
sudo ninja install
WARNING: `ninja install` will mostly install under the configured install
prefix but installs systemd service configuration directly in the system
default location `/usr/lib/systemd` so it won't work without root privileges,
even if the install prefix is a user-owned directory.