Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932376AbWIQTkS (ORCPT ); Sun, 17 Sep 2006 15:40:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932383AbWIQTkS (ORCPT ); Sun, 17 Sep 2006 15:40:18 -0400 Received: from tomts10.bellnexxia.net ([209.226.175.54]:48099 "EHLO tomts10-srv.bellnexxia.net") by vger.kernel.org with ESMTP id S932376AbWIQTkQ (ORCPT ); Sun, 17 Sep 2006 15:40:16 -0400 Date: Sun, 17 Sep 2006 15:35:01 -0400 From: Mathieu Desnoyers To: Alan Cox Cc: Andrew Morton , tglx@linutronix.de, karim@opersys.com, Paul Mundt , Jes Sorensen , Roman Zippel , Ingo Molnar , linux-kernel@vger.kernel.org, Christoph Hellwig , Ingo Molnar , Greg Kroah-Hartman , Tom Zanussi , ltt-dev@shafik.org, Michel Dagenais Subject: printk instrumentation with LTTng Message-ID: <20060917193500.GA10332@Krystal> References: <20060915135709.GB8723@localhost.usen.ad.jp> <450AB5F9.8040501@opersys.com> <450AB506.30802@sgi.com> <450AB957.2050206@opersys.com> <20060915142836.GA9288@localhost.usen.ad.jp> <450ABE08.2060107@opersys.com> <1158332447.5724.423.camel@localhost.localdomain> <20060915111644.c857b2cf.akpm@osdl.org> <1158352633.29932.141.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <1158352633.29932.141.camel@localhost.localdomain> X-Editor: vi X-Info: http://krystal.dyndns.org:8080 X-Operating-System: Linux/2.4.32-grsec (i686) X-Uptime: 15:29:05 up 25 days, 16:37, 3 users, load average: 0.18, 0.18, 0.17 User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1325 Lines: 35 * Alan Cox (alan@lxorguk.ukuu.org.uk) wrote: > In addition ideally we want a mechanism that is also sufficient that > printk can be mangled into so that you can pull all the printk text > strings _out_ of the kernel and into the debug traces for embedded work. > Further on, in LTTng 0.5.113, I added the possibility to trace the location where the printk happened. Within a huge amount of information, this kind of data identification can be very useful. Example of a printk as shown from the text dump of a trace : kernel.printk_locate: 181.713815470 (/tmp/trace2/cpu_0), 4357, 0, insmod, UNBRANDED, 4234, 0x0, SYSCALL, { file = "/home/compudj/repository/tests/kernel/test-printk.c", function = "init_module", line = 14, address = 0xf88eb000 } kernel.printk: 181.713817590 (/tmp/trace2/cpu_0), 4357, 0, insmod, UNBRANDED, 4234, 0x0, SYSCALL, { loglevel = 0, text = { printk message } } Regards, Mathieu OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/