linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tzvetomir Stoyanov <tstoyanov@vmware.com>
To: "rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: "linux-trace-devel@vger.kernel.org" <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH 4/7] tools/lib/traceevent: Implement libtraceevent man pages
Date: Wed, 7 Nov 2018 14:45:38 +0000	[thread overview]
Message-ID: <CACqStoc_Y_OD6N0CjmK5mLNykSTcnr6X=VuooFZUkb5085f0PQ@mail.gmail.com> (raw)
In-Reply-To: <20181106191556.4b199def@gandalf.local.home>

On Wed, Nov 7, 2018 at 2:15 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Tue, 6 Nov 2018 13:20:53 +0000
> Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:
>
> > This patch implements a man page, which documents
> > tep_is_host_bigendian() and tep_set_host_bigendian()
> > libtraceevent APIs
> >
> > Signed-off-by: Tzvetomir Stoyanov <tstoyanov@vmware.com>
> > ---
> >  .../libtraceevent-host_endian.txt             | 85 +++++++++++++++++++
> >  1 file changed, 85 insertions(+)
> >  create mode 100644 tools/lib/traceevent/Documentation/libtraceevent-host_endian.txt
> >
> > diff --git a/tools/lib/traceevent/Documentation/libtraceevent-host_endian.txt b/tools/lib/traceevent/Documentation/libtraceevent-host_endian.txt
> > new file mode 100644
> > index 000000000000..23e085db8d54
> > --- /dev/null
> > +++ b/tools/lib/traceevent/Documentation/libtraceevent-host_endian.txt
> > @@ -0,0 +1,85 @@
> > +libtraceevent(3)
> > +================
> > +
> > +NAME
> > +----
> > +tep_is_host_bigendian,tep_set_host_bigendian - Get / set the endianess of the local host.
>
> Probably need to state more about the endianness of the machine running
> the code. That is, the local host represents the machine executing the
> current code.

I'm confused about these two APIs:
       int tep_host_bigendian(void);
       int tep_is_host_bigendian(struct tep_handle *pevent);
Why we need the second one ? Does it work faster than the first API,
or there is some special use case ?

>
> -- Steve
>
>
> > +
> > +SYNOPSIS
> > +--------
> > +[verse]
> > +--
> > +*#include <event-parse.h>*
> > +
> > +enum *tep_endian* {
> > +     TEP_LITTLE_ENDIAN = 0,
> > +     TEP_BIG_ENDIAN
> > +};
> > +
> > +int *tep_is_host_bigendian*(struct tep_handle pass:[*]_tep_);
> > +void *tep_set_host_bigendian*(struct tep_handle pass:[*]_tep_, enum tep_endian _endian_);
> > +--
> > +
> > +DESCRIPTION
> > +-----------
> > +The _tep_is_host_bigendian()_ function returns the endianess of the local host
> > +The _tep_ argument is trace event parser context.
> > +
> > +The _tep_set_host_bigendian()_ set the endianess of the local host.
> > +The _tep_ argument is trace event parser context. The _endian_ argument is the endianess:
> > +     _TEP_LITTLE_ENDIAN_ - the host is little endian,
> > +     _TEP_BIG_ENDIAN_ - the host is big endian.
> > +
> > +RETURN VALUE
> > +------------
> > +The _tep_is_host_bigendian()_ function returns _TEP_LITTLE_ENDIAN_ or _TEP_BIG_ENDIAN_.
> > +
> > +EXAMPLE
> > +-------
> > +[source,c]
> > +--
> > +#include <event-parse.h>
> > +...
> > +struct tep_handle *tep = tep_alloc();
> > +...
> > +     tep_set_host_bigendian(tep, TEP_LITTLE_ENDIAN);
> > +...
> > +     if (TEP_BIG_ENDIAN == tep_is_host_bigendian(tep)) {
> > +             /* The local host is big endian */
> > +     } else {
> > +             /* The local host is little endian */
> > +     }
> > +--
> > +
> > +FILES
> > +-----
> > +[verse]
> > +--
> > +*event-parse.h*
> > +     Header file to include in order to have access to the library APIs.
> > +*-ltraceevent*
> > +     Linker switch to add when building a program that uses the library.
> > +--
> > +
> > +SEE ALSO
> > +--------
> > +_libtraceevent(3)_, _trace-cmd(1)_
> > +
> > +AUTHOR
> > +------
> > +[verse]
> > +--
> > +*Steven Rostedt* <rostedt@goodmis.org>, author of *libtraceevent*.
> > +*Tzvetomir Stoyanov* <tz.stoyanov@gmail.com>, author of this man page.
> > +--
> > +REPORTING BUGS
> > +--------------
> > +Report bugs to  <linux-trace-devel@vger.kernel.org>
> > +
> > +LICENSE
> > +-------
> > +libtraceevent is Free Software licensed under the GNU LGPL 2.1
> > +
> > +RESOURCES
> > +---------
> > +https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git&amp;data=02%7C01%7Ctstoyanov%40vmware.com%7C2264b262e74042761a7408d644463191%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636771465608693415&amp;sdata=FjchU9EnZ007OWjCu%2BxigDoE0IOdwmefZ0y2tdyX5JE%3D&amp;reserved=0
>


-- 
--
Tzvetomir (Ceco) Stoyanov
VMware Open Source Technology Center

  reply	other threads:[~2018-11-08  0:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 13:20 [PATCH 0/7] libtracevent man pages Tzvetomir Stoyanov
2018-11-06 13:20 ` [PATCH 1/7] tools/lib/traceevent: Implement libtraceevent " Tzvetomir Stoyanov
2018-11-06 13:20 ` [PATCH 2/7] " Tzvetomir Stoyanov
2018-11-07  0:07   ` Steven Rostedt
2018-11-06 13:20 ` [PATCH 3/7] " Tzvetomir Stoyanov
2018-11-07  0:14   ` Steven Rostedt
2018-11-06 13:20 ` [PATCH 4/7] " Tzvetomir Stoyanov
2018-11-07  0:15   ` Steven Rostedt
2018-11-07 14:45     ` Tzvetomir Stoyanov [this message]
2018-11-06 13:20 ` [PATCH 5/7] " Tzvetomir Stoyanov
2018-11-07  0:19   ` Steven Rostedt
2018-11-06 13:20 ` [PATCH 6/7] " Tzvetomir Stoyanov
2018-11-07  0:23   ` Steven Rostedt
2018-11-06 13:20 ` [PATCH 7/7] " Tzvetomir Stoyanov

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='CACqStoc_Y_OD6N0CjmK5mLNykSTcnr6X=VuooFZUkb5085f0PQ@mail.gmail.com' \
    --to=tstoyanov@vmware.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).