From castor@3pardata.com Fri Jan 10 17:20:52 2003 Received: with ECARTIS (v1.0.0; list kernprof); Fri, 10 Jan 2003 17:20:55 -0800 (PST) Received: from mail.3pardata.com (dsl-sj-66-219-79-98.broadviewnet.net [66.219.79.98]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h0B1Kq3v028513 for ; Fri, 10 Jan 2003 17:20:52 -0800 Received: from 3PARMAIL.3pardata.com (3pardata.com [192.168.32.30]) by mail.3pardata.com (8.9.3+Sun/8.9.3) with ESMTP id RAA03184 for ; Fri, 10 Jan 2003 17:26:39 -0800 (PST) Received: from marais (marais.3pardata.com [192.168.1.107]) by 3PARMAIL.3pardata.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YP3J4RYM; Fri, 10 Jan 2003 17:27:38 -0800 Date: Fri, 10 Jan 2003 17:26:37 -0800 (PST) From: Castor Fu X-X-Sender: To: Subject: kernprof on modules? (Is this list still active?) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 10 X-ecartis-version: Ecartis v1.0.0 Sender: kernprof-bounce@oss.sgi.com Errors-to: kernprof-bounce@oss.sgi.com X-original-sender: castor@3pardata.com Precedence: bulk X-list: kernprof I don't see any recent archives for this list, so I'm not sure if work is still active on kernprof. I'm interested in using the kernprof code on a kernel module. Currently everything is effectively switched off for these addresses presumably because tools like gprof are incompatible with sparse address ranges. Has anyone done much work with this? I threw together a quick hack which seems to do an adequate job of analyzing call graphs from the 'call backtrace' data using ksymoops for address resolution. It seems much easier to deal with than the gprof code. Does anyone else have plans for additions to kernprof? -castor castor@3pardata.com