From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Cc: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH 0/6 v2] trace-cmd/kernelshark: Fixed build, cleanups and fix kernelshark
Date: Wed, 16 Dec 2020 18:19:42 -0500 [thread overview]
Message-ID: <20201216231942.127326802@goodmis.org> (raw)
Sent out a v1, but the change log of patch 2 had issues that quilt
could not deal with, and was rejected. The v1 had just the first
three patches. This series has more to handle KernelShark v1 building.
Steven Rostedt (VMware) (5):
trace-cmd: Move add_event_pid() out of #ifndef NO_PTRACE
trace-cmd: Add #include <fcntl.h> to trace-cmd-private.h
trace-cmd: Add a make-trace-cmd.sh script to simplify creating a trace-cmd package
trace-cmd: Do not have local builds of libtraceevent or libtracefs use system headers
kernelshark: Build libtraceevent and libtracefs locally
Yordan Karadzhov (VMware) (1):
trace-cmd: Re-enable the build of KernelShark v1
----
Makefile | 24 ++++++++++++------
PACKAGING | 30 ++++++++++++++++++++++
kernel-shark/CMakeLists.txt | 1 +
kernel-shark/build/FindTraceCmd.cmake | 29 +++++----------------
kernel-shark/src/libkshark.c | 14 ++++++----
kernel-shark/src/libkshark.h | 2 +-
lib/trace-cmd/include/private/trace-cmd-private.h | 1 +
lib/traceevent/Makefile | 6 +++++
lib/tracefs/Makefile | 8 ++++++
make-trace-cmd.sh | 31 +++++++++++++++++++++++
tracecmd/trace-record.c | 12 ++++-----
11 files changed, 115 insertions(+), 43 deletions(-)
create mode 100644 PACKAGING
create mode 100755 make-trace-cmd.sh
next reply other threads:[~2020-12-16 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 23:19 Steven Rostedt [this message]
2020-12-16 23:19 ` [PATCH 1/6 v2] trace-cmd: Move add_event_pid() out of #ifndef NO_PTRACE Steven Rostedt
2020-12-16 23:19 ` [PATCH 2/6 v2] trace-cmd: Add #include <fcntl.h> to trace-cmd-private.h Steven Rostedt
2020-12-16 23:19 ` [PATCH 3/6 v2] trace-cmd: Add a make-trace-cmd.sh script to simplify creating a trace-cmd package Steven Rostedt
2020-12-16 23:19 ` [PATCH 4/6 v2] trace-cmd: Do not have local builds of libtraceevent or libtracefs use system headers Steven Rostedt
2020-12-16 23:19 ` [PATCH 5/6 v2] kernelshark: Build libtraceevent and libtracefs locally Steven Rostedt
2020-12-16 23:19 ` [PATCH 6/6 v2] trace-cmd: Re-enable the build of KernelShark v1 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=20201216231942.127326802@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=y.karadz@gmail.com \
/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).