From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17432 invoked by alias); 16 May 2007 16:54:23 -0000 Received: (qmail 17420 invoked by uid 22791); 16 May 2007 16:54:23 -0000 X-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_20,DK_POLICY_SIGNSOME,DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: sourceware.org Received: from e5.ny.us.ibm.com (HELO e5.ny.us.ibm.com) (32.97.182.145) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 16 May 2007 16:54:16 +0000 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e5.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l4GGsBTO002388 for ; Wed, 16 May 2007 12:54:11 -0400 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l4GGs8W4524030 for ; Wed, 16 May 2007 12:54:10 -0400 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l4GGs8VG021263 for ; Wed, 16 May 2007 12:54:08 -0400 Received: from [127.0.0.1] (wecm-9-67-45-184.wecm.ibm.com [9.67.45.184]) by d01av01.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l4GGs6eJ021062; Wed, 16 May 2007 12:54:07 -0400 Message-ID: <464B372A.80102@us.ibm.com> Date: Wed, 16 May 2007 16:54:00 -0000 From: Mike Mason User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: "Frank Ch. Eigler" CC: systemtap@sources.redhat.com Subject: Re: another war story script References: <20070511193731.GK22015@redhat.com> In-Reply-To: <20070511193731.GK22015@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00312.txt.bz2 Interesting... I haven't paid much attention to timer.profile, but now see how it can be useful. I'm probably missing something, but isn't this script essentially doing the same thing as the time accounting done via utime and stime in task_struct? Does it account for time that isn't reflected in utime and stime? Mike Frank Ch. Eigler wrote: > Hi - > > http://sources.redhat.com/systemtap/wiki/WSthreadCPUshare > > - FChE