The tracepoints can help with understanding the system behavior of a given interconnect path when the consumer drivers change their bandwidth demands. This might be interesting when we want to monitor the requested interconnect bandwidth for each client driver. The paths may share the same nodes and this will help to understand "who and when is requesting what". All this is useful for subsystem drivers developers and may also provide hints when optimizing the power and performance profile of the system. v4: - Move CREATE_TRACE_POINTS below all other headers and remove internal.h from trace.h - Picked Steven's Reviewed-by. v3: http://lore.kernel.org/r/20191122152712.19105-1-georgi.djakov@xxxxxxxxxx - In order to avoid #including a file with relative path, move the trace.h header into drivers/interconnect/. (Steven) v2: https://lore.kernel.org/r/20191101130031.27996-1-georgi.djakov@xxxxxxxxxx - Moved dev_name() into TP_fast_assign() to reduce cache footprint. (Steven) - Added path name to traces (Bjorn) - Added trace for path, device and ret. (Bjorn) v1: https://lore.kernel.org/r/20191018140224.15087-1-georgi.djakov@xxxxxxxxxx Georgi Djakov (3): interconnect: Move internal structs into a separate file interconnect: Add a name to struct icc_path interconnect: Add basic tracepoints drivers/interconnect/Makefile | 1 + drivers/interconnect/core.c | 55 +++++++++------------ drivers/interconnect/internal.h | 42 ++++++++++++++++ drivers/interconnect/trace.h | 88 +++++++++++++++++++++++++++++++++ 4 files changed, 155 insertions(+), 31 deletions(-) create mode 100644 drivers/interconnect/internal.h create mode 100644 drivers/interconnect/trace.h
