From 71c82cd299ea59afee38d905832122da65bf4bc9 Mon Sep 17 00:00:00 2001 From: Philippe Proulx Date: Fri, 25 Sep 2015 16:36:07 -0400 Subject: [PATCH] whats-new: remove LTTng-modules clock plugin This feature is for LTTng 2.8. Signed-off-by: Philippe Proulx --- contents/whats-new.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/contents/whats-new.md b/contents/whats-new.md index 8cbfd21..94b4dc5 100644 --- a/contents/whats-new.md +++ b/contents/whats-new.md @@ -14,7 +14,7 @@ LTTng 2.7 adds filtering support to kernel events as well. For example: lttng enable-event --kernel irq_handler_entry --filter 'irq == 28' -LTTng 2.7 also adds wildcard support for kernel event names: +LTTng 2.7 adds wildcard support for kernel event names:
 lttng enable-event --kernel 'sched_*'
@@ -33,10 +33,9 @@ crash requiring a reboot. The new `lttng-crash` command line
 utility can extract trace data from such a file (see
 [Recording trace data on persistent memory file systems](#doc-persistent-memory-file-systems)).
 
-LTTng-modules 2.7 and LTTng-UST 2.7 can rely on user plugins
-to provide custom clock sources to their tracer.
-LTTng-UST can also load a user plugin to retrieve the current CPU number.
-This feature exists for very advanced use cases. See
+LTTng-UST 2.7 can rely on a user plugin to provide a custom clock source
+to its tracer. LTTng-UST can also load a user plugin to retrieve the
+current CPU number. This feature exists for very advanced use cases. See
 the clock-override
 and getcpu-override
 examples for more details.
@@ -55,5 +54,7 @@ to emit enabled events.
 Moreover, LTTng 2.7 boasts great stability, benifiting from piles of
 bug fixes and more-than-welcome internal refactorings.
 
+
-- 
2.34.1