From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>,
Linux-trace Users <linux-trace-users@vger.kernel.org>
Cc: Zamir SUN <sztsian@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>,
zsun@redhat.com, Vitaly Chikunov <vt@altlinux.org>,
Tzvetomir Stoyanov <tstoyanov@vmware.com>,
Yordan Karadzhov <ykaradzhov@vmware.com>,
Ben Hutchings <ben@decadent.org.uk>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Tony Jones <tonyj@suse.de>, John Kacur <jkacur@redhat.com>,
Clark Williams <williams@redhat.com>, Al Stone <ahs3@debian.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jes Sorensen <jes.sorensen@gmail.com>
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:
https://git.kernel.org/pub/scm/utils/trace-cmd/kernel-shark.git/
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
removed.
This library lives (and will always live) with the trace-cmd repository.
https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/snapshot/trace-cmd-libtracecmd-1.1.0.tar.gz
https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/
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
tracecmd_open()
tracecmd_open_head()
tracecmd_open_fd()
tracecmd_close()
- APIs to initialize and read tracing records from a trace.dat file
tracecmd_init_data()
tracecmd_read_cpu_first()
tracecmd_read_data()
tracecmd_read_at()
tracecmd_free_record()
- APIs to retrieve the libtracevent tep handler
tracecmd_get_tep()
- APIs to manage host and guest data mappings
tracecmd_get_traceid()
tracecmd_get_guest_cpumap()
- APIs to manage the different instances existing in a trace.dat file
tracecmd_buffer_instances()
tracecmd_buffer_instance_name()
tracecmd_buffer_instance_handle()
Many more APIs will come in later releases.
Enjoy!
-- 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:
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=20210410095431.2935816f@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=ahs3@debian.org \
--cc=ben@decadent.org.uk \
--cc=jes.sorensen@gmail.com \
--cc=jkacur@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=sztsian@gmail.com \
--cc=tonyj@suse.de \
--cc=tstoyanov@vmware.com \
--cc=vt@altlinux.org \
--cc=williams@redhat.com \
--cc=ykaradzhov@vmware.com \
--cc=zsun@redhat.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).