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] libtracefs 1.1.0
Date: Sat, 10 Apr 2021 09:40:46 -0400 [thread overview]
Message-ID: <20210410094046.0a23f960@oasis.local.home> (raw)
I'm pleased to announce the new version of libtracefs library has been
released:
libtracefs: 1.1.0
https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/snapshot/libtracefs-1.1.0.tar.gz
https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/
Changes since 1.0.2:
- Depends on libtraceevent 1.2.0 or later
- New APIs for opening and reading ftrace files
tracefs_instance_file_read_number()
tracefs_instance_file_open()
- New APIs for enable / disable tracing
tracefs_trace_is_on()
tracefs_trace_on()
tracefs_trace_off()
tracefs_trace_on_get_fd()
tracefs_trace_on_fd()
tracefs_trace_off_fd()
- New APIs for trace options
tracefs_option_set()
tracefs_option_clear()
tracefs_option_is_set()
tracefs_options_get_supported()
tracefs_option_is_supported()
tracefs_options_get_enabled()
tracefs_option_is_enabled()
tracefs_option_enable()
tracefs_option_diasble()
tracefs_option_name()
tracefs_option_id()
tarcefs_option_mask_is_set()
- New APIs for getting existing trace instance
tracefs_instance_alloc()
tracefs_instance_get_trace_dir()
- New APIs to set the filtering of functions
tracefs_function_filter()
tracefs_function_notrace()
- New APIs to writing strings into the tracing buffer
tracefs_print_init()
tracefs_printf()
tracefs_vprintf()
tracefs_print_close()
- New APIs to writing binary data into the tracing buffer
tracefs_binary_init()
tracefs_binary_write()
tracefs_binary_close()
- tracefs_iterate_raw_events() now calls the callbacks in
time stamp sorted order (instead of calling all events in
a CPU buffer, then the next CPU buffer). Also fixed record->cpu
to match the CPU that's also passed to the callback, instead
of always being zero.
- Loading of events with tracefs_local_events(),
tracefs_local_event_system() and tracefs_fill_local_events()
now pull in kallsyms, saved_cmdlines, and printk_format mappings
into the tep handler.
- New API to reload the saved_cmdlines
tracefs_load_cmdlines()
- Warnings now can be overwritten with tracefs_warning() and no
longer the too generic name warning()
- All files opened in the library now are done so with O_CLOEXEC
- Cleaner building and installation.
-- Steve
next reply other threads:[~2021-04-10 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 13:40 Steven Rostedt [this message]
2021-05-18 14:23 ` [ANNOUNCE] KernelShark 2.0 Yordan Karadzhov
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=20210410094046.0a23f960@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).