From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 1/2] libtracefs: Document marker APIs
Date: Thu, 8 Apr 2021 11:09:19 +0300 [thread overview]
Message-ID: <20210408080920.3130041-2-tz.stoyanov@gmail.com> (raw)
In-Reply-To: <20210408080920.3130041-1-tz.stoyanov@gmail.com>
Added man pages describing these functions:
tracefs_marker_init()
tracefs_marker_print()
tracefs_marker_vprint()
tracefs_marker_write()
tracefs_marker_close()
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
---
Documentation/libtracefs-marker.txt | 127 ++++++++++++++++++++++++++++
1 file changed, 127 insertions(+)
create mode 100644 Documentation/libtracefs-marker.txt
diff --git a/Documentation/libtracefs-marker.txt b/Documentation/libtracefs-marker.txt
new file mode 100644
index 0000000..e2673d9
--- /dev/null
+++ b/Documentation/libtracefs-marker.txt
@@ -0,0 +1,127 @@
+libtracefs(3)
+=============
+
+NAME
+----
+tracefs_marker_init, tracefs_marker_close, tracefs_marker_print, tracefs_marker_vprint, tracefs_marker_write -
+Open, close and write data in the frace marker file.
+
+SYNOPSIS
+--------
+[verse]
+--
+*#include <tracefs.h>*
+
+int *tracefs_marker_init*(struct tracefs_instance pass:[*]_instance_);
+int *tracefs_marker_print*(struct tracefs_instance pass:[*]_instance_, const char pass:[*]_fmt_, _..._);
+int *tracefs_marker_vprint*(struct tracefs_instance pass:[*]_instance_, const char pass:[*]_fmt_, va_list _ap_);
+int *tracefs_marker_write*(struct tracefs_instance pass:[*]_instance_, void pass:[*]_data_, int _len_);
+void *tracefs_marker_close*(struct tracefs_instance pass:[*]_instance_);
+
+--
+
+DESCRIPTION
+-----------
+Set of functions to work with ftrace maker. See Documentation/trace/ftrace.rst from the Linux
+kernel tree for more information about ftrace marker functionality. All these APIs have _instance_
+as a first argument. If NULL is passed as _instance_, the top trace instance is used.
+
+The _tracefs_marker_init()_ function initializes the library for working with ftrace marker of
+the selected _instance_. It is not mandatory to call this API before working with the marker, any
+of the marker APIs will call it automatically, if the library is not yet initialized to work with
+the marker form given instance. But calling _tracefs_marker_init()_ in advance will speed up
+the other marker APIs.
+
+The _tracefs_marker_print()_ function writes a formatted string in the trace marker of the selected
+_instance_. The _fmt_ argument is a string in printf format, followed by variable arguments _..._.
+
+The _tracefs_marker_vprint()_ function writes a formatted string in the trace marker of the selected
+_instance_. The _fmt_ argument is a string in printf format, followed by list _ap_ of arguments.
+
+The _tracefs_marker_write()_ function writes a binary data in the trace marker of the selected
+_instance_. The _data_ points to the data with length _len_, that is going to be written in
+the trace marker.
+
+The _tracefs_marker_close()_ function closes the ftrace marker of the selected instance.
+
+RETURN VALUE
+------------
+The _tracefs_marker_init()_, _tracefs_marker_print()_, _tracefs_marker_vprint()_ and
+_tracefs_marker_write()_ functions return 0 if the operation is successful, or -1 in case of an error.
+
+EXAMPLE
+-------
+[source,c]
+--
+#include <tracefs.h>
+
+if (tracefs_marker_init(NULL) < 0) {
+ /* Failed to initialize the library with the ftrace marker of the top trace instance */
+}
+
+void foo_print(char *format, ...)
+{
+ va_list ap;
+ va_start(ap, format);
+ if (tracefs_marker_vprint(NULL, format, ap) < 0) {
+ /* Failed to print in the trace marker */
+ }
+ va_end(ap);
+}
+
+void foo_print_string(char *message)
+{
+ if (tracefs_marker_print(NULL, "Message from user space: %s", message) < 0) {
+ /* Failed to print in the trace marker */
+ }
+}
+
+unsigned int data = 0xdeadbeef;
+
+ if (tracefs_marker_write(NULL, &data, sizeof(data)) < 0) {
+ /* Failed to write in the trace marker */
+ }
+
+
+tracefs_marker_close();
+--
+FILES
+-----
+[verse]
+--
+*tracefs.h*
+ Header file to include in order to have access to the library APIs.
+*-ltracefs*
+ Linker switch to add when building a program that uses the library.
+--
+
+SEE ALSO
+--------
+_libtracefs(3)_,
+_libtraceevent(3)_,
+_trace-cmd(1)_,
+Documentation/trace/ftrace.rst from the Linux kernel tree
+
+AUTHOR
+------
+[verse]
+--
+*Steven Rostedt* <rostedt@goodmis.org>
+*Tzvetomir Stoyanov* <tz.stoyanov@gmail.com>
+--
+REPORTING BUGS
+--------------
+Report bugs to <linux-trace-devel@vger.kernel.org>
+
+LICENSE
+-------
+libtracefs is Free Software licensed under the GNU LGPL 2.1
+
+RESOURCES
+---------
+https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/
+
+COPYING
+-------
+Copyright \(C) 2021 VMware, Inc. Free use of this software is granted under
+the terms of the GNU Public License (GPL).
--
2.30.2
next prev parent reply other threads:[~2021-04-08 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 8:09 [PATCH 0/2] Documentation and unit tests for new trace marker APIs Tzvetomir Stoyanov (VMware)
2021-04-08 8:09 ` Tzvetomir Stoyanov (VMware) [this message]
2021-04-08 8:09 ` [PATCH 2/2] libtracefs: Unit test for " Tzvetomir Stoyanov (VMware)
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=20210408080920.3130041-2-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).