From: Steven Rostedt <rostedt@goodmis.org>
To: <linux-trace-devel@vger.kernel.org>
Cc: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: [PATCH v2 0/5] libtraceevent: Copy parsing functions from trace-cmd
Date: Thu, 8 Apr 2021 17:24:55 -0400 [thread overview]
Message-ID: <20210408212500.2058159-1-rostedt@goodmis.org> (raw)
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
Currently, trace-cmd does the work of parsing kallsyms, saved_cmdlines,
and printk_formats and feeding it to the libtraceevent tep handle. When
starting to write code snippets that work directly with libtracefs and
libtraceevent, I found that I need this functionality as well. But this
code doesn't need libtracecmd. As these files exist in /proc and in the
tracefs directly, just like we have events and headers that get parsed
by libtraceevent, add this functionality directly to libtraceevent, as
libtraceevent is made to parse files for processing of events, and all
of the above do exactly that.
Changes since version 1:
- Make this a patch series.
- Updated gitignore to ignore created files. The documentation
directory become impossible to examine with git status.
- Move all the man pages into libtraceevent-parse-files.txt as it
become obvious after writing the man page for
tep_parse_printk_formats(), that they should all be grouped together.
Steven Rostedt (VMware) (5):
libtraceevent: Update gitignore
libtraceevent: Fix dependencies in Documentation Makefile
libtraceevent: Add the API tep_parse_kallsyms()
libtraceevent: Add the API tep_parse_saved_cmdlines()
libtraceevent: Add the API tep_parse_printk_formats()
.gitignore | 5 +
Documentation/.gitignore | 3 +
Documentation/Makefile | 24 +--
Documentation/libtraceevent-parse-files.txt | 149 ++++++++++++++++++
src/event-parse.c | 161 ++++++++++++++++++++
src/event-parse.h | 3 +
6 files changed, 336 insertions(+), 9 deletions(-)
create mode 100644 Documentation/.gitignore
create mode 100644 Documentation/libtraceevent-parse-files.txt
--
2.29.2
next reply other threads:[~2021-04-08 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 21:24 Steven Rostedt [this message]
2021-04-08 21:24 ` [PATCH v2 1/5] libtraceevent: Update gitignore Steven Rostedt
2021-04-08 21:24 ` [PATCH v2 2/5] libtraceevent: Fix dependencies in Documentation Makefile Steven Rostedt
2021-04-08 21:24 ` [PATCH v2.5 3/5] libtraceevent: Add the API tep_parse_kallsyms() Steven Rostedt
2021-04-08 21:24 ` [PATCH v2 4/5] libtraceevent: Add the API tep_parse_saved_cmdlines() Steven Rostedt
2021-04-08 21:25 ` [PATCH v2 5/5] libtraceevent: Add the API tep_parse_printk_formats() 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=20210408212500.2058159-1-rostedt@goodmis.org \
--to=rostedt@goodmis.org \
--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).