Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757009AbYLOVm6 (ORCPT ); Mon, 15 Dec 2008 16:42:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755907AbYLOVmu (ORCPT ); Mon, 15 Dec 2008 16:42:50 -0500 Received: from ozlabs.org ([203.10.76.45]:32845 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754480AbYLOVmu (ORCPT ); Mon, 15 Dec 2008 16:42:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18758.53072.197695.277198@cargo.ozlabs.ibm.com> Date: Tue, 16 Dec 2008 08:42:40 +1100 From: Paul Mackerras To: Vince Weaver Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Thomas Gleixner , Andrew Morton , Stephane Eranian , Eric Dumazet , Robert Richter , Arjan van de Ven , Peter Anvin , Peter Zijlstra , "David S. Miller" , perfctr-devel@lists.sourceforge.net Subject: Re: [patch] Performance Counters for Linux, v4 In-Reply-To: References: <20081214212829.GA9435@elte.hu> X-Mailer: VM 8.0.9 under Emacs 22.2.1 (i486-pc-linux-gnu) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 882 Lines: 21 Vince Weaver writes: > I see a large (2300 instruction) fixed overhead when measuring > retired instruction count using the "timec" command > compared to the "pfmon" tool that comes with perfmon3 > (the pfmon tool has essentially no overhead when > doing aggragate counts). Looks like timec will be counting the fork() and execvp() system calls that are used to run your executable, as well as the executable itself. The fork() overhead could be removed fairly easily I think, the execvp would be hard to get rid of without using ptrace() - and the use of ptrace was one of the things that Ingo et al. objected to in perfmon3. Paul. -- 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/