Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 31 Oct 2002 09:45:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 31 Oct 2002 09:45:38 -0500 Received: from d06lmsgate-5.uk.ibm.com ([195.212.29.5]:7619 "EHLO d06lmsgate-5.uk.ibm.com") by vger.kernel.org with ESMTP id ; Thu, 31 Oct 2002 09:45:37 -0500 Subject: Re: What's left over. To: Linus Torvalds Cc: linux-kernel@vger.kernel.org, n2m1@ltc-eth1000.torolab.ibm.com, Rusty Russell X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Richard J Moore" Date: Thu, 31 Oct 2002 14:46:33 +0000 X-MIMETrack: Serialize by Router on D06ML023/06/M/IBM(Release 5.0.9a |January 7, 2002) at 31/10/2002 14:51:31 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1178 Lines: 29 >> Linux Trace Toolkit (LTT) > >I don't know what this buys us. If you consider developer productivity useful then LTT has definite benefits especially when combined with kprobes. With the two it is possible to implant tracepoints without having to code up specific printks: kprobes can be used to implant a probe, the probe handler can call LTT to record the event. Why call LTT instead of having a printk in the probe handler? - for performance reasons, for latency reasons, because kprobes can implant probes absolutely anywhere in the system, for analysis reasons - LTT trace data can be post processed and massaged in a number of ways using the visualizer tools. Yes you can do some of this using printk directly, but you can be into a whole heap more work and it will certainly take longer to implant a temporary tracepoint, recompile, run, remove, recompile the using the dynamic trace technique of LTT+kprobes. Richard - 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/