linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 5/9] libtracefs man pages: APIs for managing trace instances.
Date: Fri, 18 Dec 2020 15:08:13 -0500	[thread overview]
Message-ID: <20201218150813.5a7bbc9f@gandalf.local.home> (raw)
In-Reply-To: <20201217094626.1402191-6-tz.stoyanov@gmail.com>

On Thu, 17 Dec 2020 11:46:22 +0200
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:

> Documented APIs:
> tracefs_instance_create()
> tracefs_instance_destroy()
> tracefs_instance_free()
> tracefs_instance_is_new()
> 
> Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
> ---
>  Documentation/libtracefs-instances-manage.txt | 104 ++++++++++++++++++
>  1 file changed, 104 insertions(+)
>  create mode 100644 Documentation/libtracefs-instances-manage.txt
> 
> diff --git a/Documentation/libtracefs-instances-manage.txt b/Documentation/libtracefs-instances-manage.txt
> new file mode 100644
> index 0000000..ca08269
> --- /dev/null
> +++ b/Documentation/libtracefs-instances-manage.txt
> @@ -0,0 +1,104 @@
> +libtracefs(3)
> +=============
> +
> +NAME
> +----
> +tracefs_instance_create, tracefs_instance_destroy, tracefs_instance_free,
> +tracefs_instance_is_new - Manage trace instances.
> +
> +SYNOPSIS
> +--------
> +[verse]
> +--
> +*#include <tracefs.h>*
> +
> +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_);
> +
> +--
> +
> +DESCRIPTION
> +-----------
> +This set of functions can be used to manage trace instances.

We should add a description of what a trace instance is:

 "A trace instance is a sub buffer used by the Linux tracing system. Given
 a unique name, the events enabled in an instance do not affect the main
 tracing system, nor other instances, as events enabled in the main tracing
 system or other instances do not affect the given instance."



> +
> +The _tracefs_instance_create()_ function creates a new trace instance with given
> +_name_, if it does not already exist in the system. It allocates and initializes
> +a new tracefs_instance structure and returns it.

The above description is a little ambiguous to what happen if the instance
already exists in the system. Perhaps reword the above to:

 "The _tracefs_instance_create()_ function allocates and initializes a new
 tracefs_instance structure and returns it. If the instance does not yet
 exist in the system, it will be created."

> +
> +The _tracefs_instance_destroy()_ destroys the trace _instance_ and frees the
> +tracefs_instance structure.

 "The _tracefs_instance_destroy()_ frees the _instance_ structure, and will
 also remove the trace instance from the system."


> +
> +The _tracefs_instance_free()_ function frees the tracefs_instance structure,
> +without destroying the trace instance.
> +
> +The _tracefs_instance_is_new()_ function checks if the given _instance_ is newly
> +created by _tracefs_instance_create()_, or it has been in the system before that.

 "The _tracefs_instance_is_new()_ function returns true if the
 _tracefs_instance_create() that allocated _instance_ also created the
 trace instance in the system, or false if the trace instance already
 existed in the system when _instance_ was allocated by
 _tracefs_instance_create()_.

-- Steve

> +
> +RETURN VALUE
> +------------
> +The _tracefs_instance_create()_ function returns a pointer to a newly allocated
> +tracefs_instance structure. It must be freed with _tracefs_instance_destroy()_ or
> +_tracefs_instance_free()_.
> +
> +The _tracefs_instance_destroy()_ function returns -1 in case of an error,
> +or 0 otherwise.
> +
> +The _tracefs_instance_is_new()_ function returns true if the instance is
> +created by _tracefs_instance_create()_ or false if it was in the system
> +before that.
> +
> +

  reply	other threads:[~2020-12-18 20:09 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
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 [this message]
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=20201218150813.5a7bbc9f@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).