All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev@lists.lttng.org, diamon-discuss@lists.linuxfoundation.org
Subject: [diamon-discuss] [RELEASE] LTTng-UST 2.10.0-rc2, 2.9.1, 2.8.3 (Linux user-space tracer)
Date: Mon, 12 Jun 2017 22:32:16 +0000 (UTC)	[thread overview]
Message-ID: <1320157800.11332.1497306736485.JavaMail.zimbra@efficios.com> (raw)

LTTng-UST, the Linux Trace Toolkit Next Generation Userspace Tracer,
is a low-overhead application tracer. The library "liblttng-ust" enables
tracing of applications and libraries.

The 2.10.0-rc2 release contains an important change to the newly
introduced "blocking UST ring buffer" interface:

    Introduce the LTTNG_UST_ALLOW_BLOCKING env. var. to control whether
    applications are allowed to block when a buffer is full. If set, it
    allows the tracer to block the application when buffers are full.
    
    The blocking is now controlled by a per-channel configuration option in
    the LTTng control interface for channels with the "--blocking-timeout"
    parameter, which is specified in usec (or -1 to block forever).
    
    This replaces the LTTNG_UST_BLOCKING_RETRY_TIMEOUT env. var., which
    actually never made it into a stable release (we therefore remove this
    env. var).

This will allow a much more fine-grained control over which channel
end up having a blocking behavior, allowing, for instance, to only
send part of the application events to a blocking buffer, and other
events to a buffer that discards events when full. This change is
introduced in locked-step in lttng-tools 2.10.0-rc2 (which is
expected to be released on June 13). This new environment variable
is described in the lttng-ust(3) man page.

The rest of the changes are mainly bug fixes and documentation
improvements.

Enjoy!

Mathieu

Project website: http://lttng.org
Documentation: http://lttng.org/docs
Download link: http://lttng.org/download

Changelog:

2017-06-12 (National Peanut Butter Cookie Day) lttng-ust 2.10.0-rc2
        * Introduce LTTNG_UST_ALLOW_BLOCKING env. var.
        * Fix: lttng-ust-elf.c: define NT_GNU_BUILD_ID if not defined
        * Fix: Quote CMAKE variable assignment in Makefile
        * Rework configure script
        * Fix: Typo in doc/examples/Makefile.am
        * Fix: Don't override user variables within the build system
        * Move m4 scripts to m4 dir
        * doc: remove duplicate LTTNG_UST_BLOCKING_RETRY_TIMEOUT man page entry

2017-06-12 (National Peanut Butter Cookie Day) lttng-ust 2.9.1
        * Fix: lttng-ust-elf.c: define NT_GNU_BUILD_ID if not defined
        * Fix: Quote CMAKE variable assignment in Makefile
        * Fix: Typo in doc/examples/Makefile.am
        * Fix: Don't override user variables within the build system
        * Fix: add missing getenv.h include to ustctl.c
        * Fix: race between lttng-ust getenv() and application setenv()
        * doc/man: add typical `$` and `#` prompts to command lines
        * Fix: (un)install targets of Python agent
        * Fix: include config.h to resolve HAVE_DLMOPEN
        * Validate the presence of dlmopen at configure time
        * Fix: CMake examples integration
        * doc/examples/Makefile.am: define C and C++ compilers for CMake

2017-06-12 (National Peanut Butter Cookie Day) lttng-ust 2.8.3
        * Fix: lttng-ust-elf.c: define NT_GNU_BUILD_ID if not defined
        * Fix: Don't override user variables within the build system
        * Fix: add missing getenv.h include to ustctl.c
        * Fix: race between lttng-ust getenv() and application setenv()
        * doc/man: add typical `$` and `#` prompts to command lines
        * Fix: (un)install targets of Python agent

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

                 reply	other threads:[~2017-06-12 22:32 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=1320157800.11332.1497306736485.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=lttng-dev@lists.lttng.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.