From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev <lttng-dev@lists.lttng.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [RELEASE] LTTng-modules 2.9.9 (Linux kernel tracer)
Date: Wed, 9 May 2018 14:15:18 -0400 (EDT) [thread overview]
Message-ID: <1944310744.230.1525889718516.JavaMail.zimbra@efficios.com> (raw)
This is a bugfix update of the stable-2.9 series of the LTTng modules
project. It updates support to kernel 4.17-rc4 as well.
Thanks,
Mathieu
Project website: http://lttng.org
Documentation: http://lttng.org/docs
Download link: http://lttng.org/download
Changelog:
2018-05-09 (Lost Sock Memorial Day) LTTng modules 2.9.9
* Fix: update RCU instrumentation for 4.17
* Fix: sunrpc instrumentation for 4.17
* Fix: use struct reclaim_stat in mm_vmscan_lru_shrink_inactive for 4.17
* Fix: Add gfp_flags arg to mm_vmscan_kswapd_wake for 4.17
* Update: kvm instrumentation for ubuntu 4.13.0-38
* Fix: update kvm instrumentation for Ubuntu 3.13.0-144
* Fix: btrfs instrumentation namespacing
* Cleanup: comment about CONFIG_HOTPLUG_CPU ifdef
* Fix: do not use CONFIG_HOTPLUG_CPU for the new hotplug API
* Fix: update kvm instrumentation for 4.1.50+
* Use the memory pool instead of kmalloc
* Create a memory pool for temporary tracepoint probes storage
* Fix: use proper pid_ns in the process statedump
* Fix: add variable quoting to shell scripts
* Update: kvm instrumentation for fedora 4.14.13-300
* Fix: Add Fedora version macros
* Fix: update btrfs instrumentation for SuSE 4.4.114-92
* Fix: update block instrumentation for SuSE 4.4.114-92
* Fix: update rcu instrumentation for v4.16
* Fix: update vmscan instrumentation for v4.16
* Fix: update timer instrumentation on 4.16 and 4.14-rt
* Update kvm instrumentation for debian kernel 4.14.0-3
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
reply other threads:[~2018-05-09 18:15 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=1944310744.230.1525889718516.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--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).