From cff67ebe90fc083a014bf8b2dae0c120b3201d1d Mon Sep 17 00:00:00 2001 From: Mathieu Desnoyers Date: Fri, 4 Nov 2011 06:50:02 -0400 Subject: [PATCH] Update trace clock warning to match the current development plan Signed-off-by: Mathieu Desnoyers --- wrapper/trace-clock.h | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/wrapper/trace-clock.h b/wrapper/trace-clock.h index b2a90bd4..11bef42b 100644 --- a/wrapper/trace-clock.h +++ b/wrapper/trace-clock.h @@ -60,11 +60,10 @@ static inline int get_trace_clock(void) printk(KERN_WARNING " * NMIs will not be traced,\n"); printk(KERN_WARNING " * expect significant performance degradation compared to the\n"); printk(KERN_WARNING " LTTng trace clocks.\n"); - printk(KERN_WARNING "You should consider deploying a kernel with the the LTTng kernel\n"); - printk(KERN_WARNING "patches, or, better, ask the Linux tracing maintainers to integrate\n"); - printk(KERN_WARNING "them if you care deeply about this.\n"); + printk(KERN_WARNING "Integration of the LTTng 0.x trace clocks into LTTng 2.0 is planned\n"); + printk(KERN_WARNING "in a near future.\n"); -#warning "LTTng: Using mainline kernel monotonic clock. NMIs will not be traced, and expect significant performance degradation compared to the LTTng trace clocks. You should consider deploying a kernel with the the LTTng kernel patches, or, better, ask the Linux tracing maintainers to integrate them if you care deeply about this." +#warning "LTTng: Using mainline kernel monotonic clock. NMIs will not be traced, and expect significant performance degradation compared to the LTTng trace clocks. Integration of the LTTng 0.x trace clocks into LTTng 2.0 is planned in a near future." return 0; } -- 2.34.1