linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev@lists.lttng.org,
	diamon-discuss@lists.linuxfoundation.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [RELEASE] LTTng-modules 2.8.5 and 2.9.2 (Linux kernel tracer)
Date: Tue, 25 Apr 2017 14:10:52 +0000 (UTC)	[thread overview]
Message-ID: <990889229.18527.1493129452235.JavaMail.zimbra@efficios.com> (raw)

Hi!

These new releases of LTTng-modules (2.8.5 and 2.9.2) mainly adapt
actively maintained stable branches (stable-2.8 and stable-2.9) to
build on 4.10 and 4.11-rc8 Linux kernels.

LTTng-modules 2.9.1 already supported the 4.10 kernel. Therefore,
2.9.2 adds support for 4.11-rc8 kernel to the stable-2.9 branch,
and 2.8.5 adds support for the 4.10 and 4.11-rc8 kernels to the
stable-2.8 branch.

Don't forget to enjoy a delicious zucchini bread today !

Enjoy!

Mathieu

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

Changelog:

2017-04-25 (National Zucchini Bread Day) LTTng modules 2.8.5
        * Revert "Documentation: lttng-modules 2.8 supports Linux < 4.10"
        * Fix: kref changes for kernel 4.11
        * Fix: timers cputime_t arguments replaced by ull in kernel 4.11
        * Fix: update scsi instrumentation for kernel 4.11
        * Fix: changes to the vm_op fault cb prototype in libringbuffer
        * Fix: update btrfs instrumentation for kernel 4.11
        * Fix: update mm_vmscan instrumentation for kernel 4.11
        * Fix: only include linux/cpuhotplug.h for kernels >= 4.10
        * Fix: 4.10 hotplug adaptation backward compat
        * Adapt lttng-modules to Linux 4.10 cpu hotplug state machine
        * Fix: 4.10 btrfs instrumentation update backward compat
        * Update btrfs instrumentation for 4.10 kernel
        * btrfs instrumentation: update to 4.10 kernel
        * timer instrumentation: adapt to ktime_t without union
        * Fix: Always build vmscan probe
        * Fix: use of uninitialized ret value in lttng_abi_open_metadata_stream
        * Fix: atomic_add_unless() returns true/false rather than prior value
        * Documentation: lttng-modules 2.8 supports Linux < 4.10

2017-04-25 (National Zucchini Bread Day) LTTng modules 2.9.2
        * Fix: Always build vmscan probe
        * Fix: use of uninitialized ret value in lttng_abi_open_metadata_stream
        * Fix: kref changes for kernel 4.11
        * Fix: atomic_add_unless() returns true/false rather than prior value
        * Fix: timers cputime_t arguments replaced by ull in kernel 4.11
        * Fix: update scsi instrumentation for kernel 4.11
        * Fix: changes to the vm_op fault cb prototype in libringbuffer
        * Fix: update btrfs instrumentation for kernel 4.11
        * Fix: update mm_vmscan instrumentation for kernel 4.11
        * Fix: section mismatch warning caused by __exit annotation


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

                 reply	other threads:[~2017-04-25 14:09 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=990889229.18527.1493129452235.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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 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).