On Wed, 9 Dec 2020 15:41:36 +0200 "Yordan Karadzhov (VMware)" <y.karadz@xxxxxxxxx> wrote: > In this patch-set we are starting the introduction of the changes > in the C API of libkshark. The goal of this transformation is to > turn KernelShark into a general purpose toolkit for analysis of > tracing data that is no longer strongly coupled to the Ftrace/trace-cmd > data format. At the end of the transformation KernelShark will be able > to merge and simultaneously visualize data from different tracers, > recorded in different data formats. It will also significantly extend > the possibilities for user customization. > > This patch-set transforms the way KernelShark processes the raw tracing > data. Later, in a consecutive patch-sets we will introduce the changes > in the visualization instruments and in the KernelShark GUI itself. > > Steven, > I believe all patches in this set are ready to move upstream. > Thanks Yordan, I just realized that the current repo doesn't build against the latest libtracefs, because the library's location has moved. I noticed that the CMake files have it hard coded with: find_library(TRACEFS_LIBRARY NAMES tracefs/libtracefs.a find_library(TRACEFS_LIBRARY NAMES tracefs/libtracefs.so) Is there a way to make cmake use pkg-config? pkg-config --cflags --libs libtracefs Will give us the correct includes and libraries for building against libtracefs if installed. We'll want the same for libtraceevent and libtracecmd as well. -- Steve
|