From: Steven Rostedt <rostedt@goodmis.org>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 2/9] libtracefs: Initial support for man pages
Date: Fri, 18 Dec 2020 13:49:09 -0500 [thread overview]
Message-ID: <20201218134909.77bdeda6@gandalf.local.home> (raw)
In-Reply-To: <20201217094626.1402191-3-tz.stoyanov@gmail.com>
On Thu, 17 Dec 2020 11:46:19 +0200
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
> +SYNOPSIS
> +--------
> +[verse]
> +--
> +*#include <tracefs.h>*
> +*#include <event-parse.h>*
tracefs.h already includes event-parse.h, and when it is installed, it's
not in the standard search path (unless you add pkg-config libtraceevent).
I would remove the reference to event-parse.h.
-- Steve
> +
> +Locations of tracing files and directories:
> + char pass:[*]*tracefs_get_tracing_file*(const char pass:[*]_name_);
> + void *tracefs_put_tracing_file*(char pass:[*]_name_);
> + const char pass:[*]*tracefs_get_tracing_dir*(void);
> + char pass:[*]*tracefs_find_tracing_dir*(void);
> +
> +Trace instances:
> + struct tracefs_instance pass:[*]*tracefs_instance_create*(const char pass:[*]_name_);
> + int *tracefs_instance_destroy*(struct tracefs_instance pass:[*]_instance_);
> + void *tracefs_instance_free*(struct tracefs_instance pass:[*]_instance_);
> + bool *tracefs_instance_is_new*(struct tracefs_instance pass:[*]_instance_);
> + bool *tracefs_file_exists*(struct tracefs_instance pass:[*]_instance_, char pass:[*]_name_);
> + bool *tracefs_dir_exists*(struct tracefs_instance pass:[*]_instance_, char pass:[*]_name_);
> + char pass:[*]*tracefs_instance_get_file*(struct tracefs_instance pass:[*]_instance_, const char pass:[*]_file_);
> + char pass:[*]*tracefs_instance_get_dir*(struct tracefs_instance pass:[*]_instance_);
> + int *tracefs_instance_file_write*(struct tracefs_instance pass:[*]_instance_, const char pass:[*]_file_, const char pass:[*]_str_);
> + char pass:[*]*tracefs_instance_file_read*(struct tracefs_instance pass:[*]_instance_, char pass:[*]_file_, int pass:[*]_psize_);
> + const char pass:[*]*tracefs_instance_get_name*(struct tracefs_instance pass:[*]_instance_);
> + int *tracefs_instances_walk*(int (pass:[*]_callback_)(const char pass:[*], void pass:[*]), void pass:[*]_context)_;
> + bool *tracefs_instance_exists*(const char pass:[*]_name_);
> +
> +Trace events:
> + char pass:[*]pass:[*]*tracefs_event_systems*(const char pass:[*]_tracing_dir_);
> + char pass:[*]pass:[*]*tracefs_system_events*(const char pass:[*]_tracing_dir_, const char pass:[*]_system_);
> + int *tracefs_iterate_raw_events*(struct tep_handle pass:[*]_tep_, struct tracefs_instance pass:[*]_instance_, cpu_set_t pass:[*]_cpus_, int _cpu_size_, int (pass:[*]_callback_)(struct tep_event pass:[*], struct tep_record pass:[*], int, void pass:[*]), void pass:[*]_callback_context_);
> + struct tep_handle pass:[*]*tracefs_local_events*(const char pass:[*]_tracing_dir_);
> + struct tep_handle pass:[*]*tracefs_local_events_system*(const char pass:[*]_tracing_dir_, const char pass:[*] const pass:[*]_sys_names_);
> + int *tracefs_fill_local_events*(const char pass:[*]_tracing_dir_, struct tep_handle pass:[*]_tep_, int pass:[*]_parsing_failures_);
> +
> +Trace helper functions:
> + void *tracefs_list_free*(char pass:[*]pass:[*]_list_);
> + char pass:[*]pass:[*]*tracefs_tracers*(const char pass:[*]_tracing_dir_);
> + char pass:[*]*tracefs_get_clock*(struct tracefs_instance pass:[*]_instance_);
> +--
next prev parent reply other threads:[~2020-12-18 18:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 9:46 [PATCH 0/9] libtracefs man pages Tzvetomir Stoyanov (VMware)
2020-12-17 9:46 ` [PATCH 1/9] libtracefs: Remove doc_gui targets Tzvetomir Stoyanov (VMware)
2020-12-18 19:24 ` Steven Rostedt
2020-12-17 9:46 ` [PATCH 2/9] libtracefs: Initial support for man pages Tzvetomir Stoyanov (VMware)
2020-12-18 18:49 ` Steven Rostedt [this message]
2020-12-17 9:46 ` [PATCH 3/9] libtracefs man pages: APIs for locating trace directory and files Tzvetomir Stoyanov (VMware)
2020-12-18 18:55 ` Steven Rostedt
2020-12-21 3:44 ` Tzvetomir Stoyanov
2020-12-21 4:10 ` Steven Rostedt
2020-12-21 5:03 ` Tzvetomir Stoyanov
2020-12-17 9:46 ` [PATCH 4/9] libtracefs man pages: APIs for working with trace systems and events Tzvetomir Stoyanov (VMware)
2020-12-18 19:23 ` Steven Rostedt
2020-12-17 9:46 ` [PATCH 5/9] libtracefs man pages: APIs for managing trace instances Tzvetomir Stoyanov (VMware)
2020-12-18 20:08 ` Steven Rostedt
2020-12-17 9:46 ` [PATCH 6/9] libtracefs man pages: APIs for working with files in " Tzvetomir Stoyanov (VMware)
2020-12-18 20:27 ` Steven Rostedt
2020-12-17 9:46 ` [PATCH 7/9] libtracefs man pages: helper APIs for working with " Tzvetomir Stoyanov (VMware)
2020-12-18 23:33 ` Steven Rostedt
2020-12-17 9:46 ` [PATCH 8/9] libtracefs man pages: APIs for initializing a tep handler with trace events from the local system Tzvetomir Stoyanov (VMware)
2020-12-17 9:46 ` [PATCH 9/9] libtracefs man pages: helper APIs for working with trace file system 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=20201218134909.77bdeda6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@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).