From owner-kernprof@oss.sgi.com Fri Dec 7 15:12:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fB7NCw326672 for kernprof-outgoing; Fri, 7 Dec 2001 15:12:58 -0800 Received: (from hawkes@localhost) by oss.sgi.com (8.11.2/8.11.3) id fB7NCti26668 for kernprof@oss.sgi.com; Fri, 7 Dec 2001 15:12:55 -0800 Date: Fri, 7 Dec 2001 15:12:55 -0800 From: John Hawkes Message-Id: <200112072312.fB7NCti26668@oss.sgi.com> To: kernprof@oss.sgi.com Subject: new kernprof patch available for 2.4.16 kernel Sender: owner-kernprof@oss.sgi.com Precedence: bulk FYI, a new kernprof kernel patch and associated kernprof command are now available at: http://oss.sgi.com/projects/kernprof/download The file profile-0.11-2.4.16.patch.gz is a patch against the 2.4.16 kernel, and the file kernprof-1.4.tar.gz is a compatible kernprof command. This version 0.11 of the kernel patch differs from the previous version 0.10.4 in supporting a new kernprof command arg, -p , with which you can focus your profiling on a single process, instead of capturing profiling data on the entirety of kernel activity. The new kernprof command, version 1.4, supports this new argument. It is believed that the previous kernprof command, version 1.3.2, is compatible with the new kernel patch 0.11, although of course this older kernprof command doesn't understand the new "-p " argument. It is also believed tha the new kernprof command, version 1.4, is compatible with the previous kernel patch, version 0.10.3, although of course the older kernel won't understand that "-p " request. John Hawkes hawkes@sgi.com From owner-kernprof@oss.sgi.com Mon Dec 10 11:26:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fBAJQZu12544 for kernprof-outgoing; Mon, 10 Dec 2001 11:26:35 -0800 Received: from thalia.fm.intel.com (fmfdns02.fm.intel.com [132.233.247.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fBAJQWo12537 for ; Mon, 10 Dec 2001 11:26:32 -0800 Received: from fmsmsxvs041.fm.intel.com (fmsmsxv041-1.fm.intel.com [132.233.48.109]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.46 2001/10/25 21:02:55 root Exp $) with SMTP id SAA28219 for ; Mon, 10 Dec 2001 18:26:31 GMT Received: from fmsmsx26.fm.intel.com ([132.233.42.26]) by fmsmsxvs041.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2001121010274025513 for ; Mon, 10 Dec 2001 10:27:40 -0800 Received: by fmsmsx26.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 10 Dec 2001 10:26:31 -0800 Message-ID: <01BDB7EEF8D4D3119D95009027AE999506C2D5C9@FMSMSX33> From: "Smith, Stan" To: "'kernprof@oss.sgi.com'" Subject: Kernel module profiling support Date: Mon, 10 Dec 2001 10:26:25 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-kernprof@oss.sgi.com Precedence: bulk FYI - In an attempt to not make this an RTFM answer, I checked the FAQ and read all online docs. The question remains..... What is the status of profiling support for loaded kernel modules? Call backtrace profiling looked promising in that it uses /proc/ksyms. Sadly I was unable to inform gprof about loaded module symbols? What am I missing here? Intel Project: Linux InfiniBand I/O stack development. Given the layered IB code is developed by three different groups and specifically designed as loaded modules, static linking the code into the kernel is an undesirable time sink at this juncture. Therefore profiling kernel modules is about the only way to move from beta code to full performance. Thank you, Stan C. Smith.