From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: linux-trace-devel@vger.kernel.org
Cc: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH 0/2] New plugins for KS 2.0
Date: Thu, 29 Apr 2021 18:44:19 +0300 [thread overview]
Message-ID: <20210429154421.255872-1-y.karadz@gmail.com> (raw)
This patch applies on top of the
"(Not so) Minor fixes toward KS 2.0" v2 patch-set.
Yordan Karadzhov (VMware) (2):
kernel-shark: Add EventFieldPlot plugin
kernel-shark: Add LatencyPlot plugin
src/plugins/CMakeLists.txt | 10 +
src/plugins/EventFieldDialog.cpp | 183 ++++++++++++++++++
src/plugins/EventFieldDialog.hpp | 60 ++++++
src/plugins/EventFieldPlot.cpp | 109 +++++++++++
src/plugins/LatencyPlot.cpp | 305 ++++++++++++++++++++++++++++++
src/plugins/LatencyPlotDialog.cpp | 184 ++++++++++++++++++
src/plugins/LatencyPlotDialog.hpp | 59 ++++++
src/plugins/event_field_plot.c | 125 ++++++++++++
src/plugins/event_field_plot.h | 64 +++++++
src/plugins/latency_plot.c | 168 ++++++++++++++++
src/plugins/latency_plot.h | 62 ++++++
tests/libkshark-gui-tests.cpp | 2 +
12 files changed, 1331 insertions(+)
create mode 100644 src/plugins/EventFieldDialog.cpp
create mode 100644 src/plugins/EventFieldDialog.hpp
create mode 100644 src/plugins/EventFieldPlot.cpp
create mode 100644 src/plugins/LatencyPlot.cpp
create mode 100644 src/plugins/LatencyPlotDialog.cpp
create mode 100644 src/plugins/LatencyPlotDialog.hpp
create mode 100644 src/plugins/event_field_plot.c
create mode 100644 src/plugins/event_field_plot.h
create mode 100644 src/plugins/latency_plot.c
create mode 100644 src/plugins/latency_plot.h
--
2.27.0
next reply other threads:[~2021-04-29 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 15:44 Yordan Karadzhov (VMware) [this message]
2021-04-29 15:44 ` [PATCH 1/2] kernel-shark: Add EventFieldPlot plugin Yordan Karadzhov (VMware)
2021-04-29 15:44 ` [PATCH 2/2] kernel-shark: Add LatencyPlot plugin Yordan Karadzhov (VMware)
2021-05-06 19:33 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210429154421.255872-1-y.karadz@gmail.com \
--to=y.karadz@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).