From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755241Ab0I3H7n (ORCPT ); Thu, 30 Sep 2010 03:59:43 -0400 Received: from one.firstfloor.org ([213.235.205.2]:49633 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755149Ab0I3H7m (ORCPT ); Thu, 30 Sep 2010 03:59:42 -0400 From: Andi Kleen To: Venkatesh Pallipadi Cc: Peter Zijlstra , Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner , Balbir Singh , linux-kernel@vger.kernel.org, Paul Turner , Eric Dumazet Subject: Re: Proper kernel irq time accounting -v3 References: <1285788096-29471-1-git-send-email-venki@google.com> Date: Thu, 30 Sep 2010 09:59:40 +0200 In-Reply-To: <1285788096-29471-1-git-send-email-venki@google.com> (Venkatesh Pallipadi's message of "Wed, 29 Sep 2010 12:21:29 -0700") Message-ID: <8762xnwtjn.fsf@basil.nowhere.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Venkatesh Pallipadi writes: > > Solution to (1) involves adding extra timing on irq entry/exit to > get the fine granularity info and then exporting it to user. This means RDTSC right? I am a bit concerned about overhead on systems with high TSC overhead. Is there a way to turn this off at runtime for those? -Andi -- ak@linux.intel.com -- Speaking for myself only.