6ead0097de
build: fix warnings for release builds
2018-08-22 13:06:15 -07:00
50ccd73592
visualizers: use double instead of float
...
To give us less changes of incorrect values when converting between scales
(at the cost of 2x the array size).
2018-06-16 20:22:53 -07:00
a1e3d06296
cpu: make row a bit bigger
...
We should make it at least the size of the minimum for the view area, or
things look weird when we dont have marks added.
2018-06-16 19:48:23 -07:00
8a4318d4f1
fps: use fill for fps line
2018-05-20 15:51:35 -07:00
0535691afa
line-visualizer: add support for filling line areas
...
This allows us to fill the area and set it to an RGBA instead of the same
as the line color itself.
2018-05-20 15:51:35 -07:00
fc0eff6d4b
visualizers: add comment about how to add data visualizers
2018-05-20 15:51:35 -07:00
2e54a1766e
visualizers: tweak row heights
2018-05-18 17:50:33 +01:00
12f627a7bd
fps: discover gtk FPS counter and add visualizer row
2018-05-17 20:31:56 +01:00
138f08d4fe
line-visualizer: clear line info to visible black
2018-05-17 20:31:29 +01:00
c734f59ba5
mark: use gslice for inferred rect
...
We can get a little boost by using the gslice allocator for the structs
of the same size.
2018-05-17 19:42:10 +01:00
94bb2fba0d
visualizer: Make proper rectangles from i915 GPU events.
...
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.
2018-05-17 19:36:01 +01:00
9381ae3070
rectangles: add basic tooltip support
...
We definitely want to do something better, but this at least allows testing
some data which is useful now to see what is going on.
2018-05-16 16:33:46 +01:00
a15eb358ce
visualizer: ignore anchor x/y position
...
We don't need that, and it breaks for things not at index 0,0.
2018-05-16 15:09:20 +01:00
88af69c3ec
visualizers: mark fields as private
2018-05-16 12:44:48 +01:00
af3e3b0e2a
marks: start on visualizer row data for marks
...
This is sort of a minimal implementation to get started. There is still
plenty to do, but we can iterate from here.
2018-05-16 12:44:48 +01:00
0e9f4ca291
visualizers: limit mark rows to 30
2018-05-16 12:44:48 +01:00
14d2554c35
marks: add group to visualizer row
...
This will allow us to filter events that we do not care about for a given
row. We add a visualizer row per-group.
2018-05-16 12:44:48 +01:00
4f9ea0fce8
visualizers: discover group types when locating mark types
2018-05-16 12:44:48 +01:00
540ff0e05d
marks: stub out a visualizer row
...
This doesn't do any rendering yet, but it gets us the plumbing we need to
start rendering mark content into a visualizer row.
2018-05-16 12:44:48 +01:00
6fa2c270e8
visualizers: discover visualizers from capture reader
...
The goal here is to avoid having to hard code what visualizers are shown
from the .ui files. We just should add things that we find are supported.
Long term, I think we'll add a concept of an "instrument" which is the
combination of a data source (SpSource) and a visualizer (SpVisualizerRow).
The other goal here is to enable the future support for discovering marks
and adding rows for each of those threads.
2018-05-16 12:44:48 +01:00
eb6fdffa6f
visualizers: fix whitespace
2018-05-15 11:35:01 +01:00
6e8c30dfa3
line-visualizer: use array for pointers and mark private
2018-05-15 10:02:58 +01:00
00b6892a72
build: fix header installation paths
2017-09-28 17:45:07 -07:00
190faa818d
build: use subdir meson.build files
...
This keeps the build file closer to the sources it effects.
2017-09-28 16:57:00 -07:00
c47822b26e
source tree cleanup
...
The lib/ directory was getting a bit out of hand, so this tries
to organize things a bit so it is easier going forward to locate
the code people want to patch.
2017-09-28 16:23:03 -07:00
