archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <>
To: LKML <>,
	Linux-trace Users <>
Cc: Zamir SUN <>,
	Arnaldo Carvalho de Melo <>,
	Jiri Olsa <>,, Vitaly Chikunov <>,
	Tzvetomir Stoyanov <>,
	Yordan Karadzhov <>,
	Ben Hutchings <>,
	Sudip Mukherjee <>,
	Tony Jones <>, John Kacur <>,
	Clark Williams <>, Al Stone <>,
	Mauro Carvalho Chehab <>,
	Jes Sorensen <>
Subject: [ANNOUNCE] libtracececmd 1.0.0
Date: Sat, 10 Apr 2021 09:54:31 -0400	[thread overview]
Message-ID: <20210410095431.2935816f@oasis.local.home> (raw)

This is the initial official release of libtracecmd 1.0.0. This is
needed by KernelShark in order to be in a stand alone repository:

All new development for KernelShark now takes place in the above
repository, which will depend on this library. The code that exists
currently in the trace-cmd.git repository for KernelShark will be

This library lives (and will always live) with the trace-cmd repository.

The purpose of his library is to be able to create and read the
trace.dat file that trace-cmd produces. It may also include
functionality to start trace recordings and other features provided by
trace-cmd itself. But for this release, it only contains the bare
necessities that a stand alone KernelShark requires.

The current API for this release are:

 - APIs to open and close a trace.dat file

 - APIs to initialize and read tracing records from a trace.dat file

 - APIs to retrieve the libtracevent tep handler

 - APIs to manage host and guest data mappings

 - APIs to manage the different instances existing in a trace.dat file

Many more APIs will come in later releases.


-- Steve

                 reply	other threads:[~2021-04-10 13:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210410095431.2935816f@oasis.local.home \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).