From: Steven Rostedt <rostedt@goodmis.org>
To: "linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>
Subject: [ANNOUNCE] libtracefs v1.7 is released
Date: Wed, 7 Jun 2023 19:29:28 -0400 [thread overview]
Message-ID: <20230607192928.50b51b2b@gandalf.local.home> (raw)
https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/tag/?h=libtracefs-1.7.0
libtracefs 1.7
Changes since libtracefs 1.6.4
New API:
- tracefs_instance_reset() to reset a tracefs instance like trace-cmd reset
does.
- Added keyword stacktrace to tracefs_sql() to be able to pass and set
stacktraces between events.
- tracefs_instance_tracers() that shows the available traces for an instance.
Currently there's only tracefs_tracers() which only give the top level
tracers, but instances may have a limited set.
- tracefs_synth_set_instance() to set the instance that does the work to make
the synthetic event such that the histograms it uses does not affect the top
level or other instance.
- tracefs_find_cid_pid() helper used to map the main guest thread to a given
vsocket CID.
- tracefs_time_conversion() helper function that does a perf system call to
find out what the multiplier and shift that the kernel uses to calculate
nanoseconds from the CPU time stamp counter.
- tracefs_kprobe_destory() used to complement tracefs_kprobe_raw() and
tracefs_kretprobe_raw(), as those do not return descriptors that can be used
to delete the kprobe and kretprobe.
Updates:
- Fixes to the tests.
- Added meson build support (but it is not the default).
https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/
Enjoy!
-- Steve
reply other threads:[~2023-06-07 23:29 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=20230607192928.50b51b2b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.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).