From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [RFC 1/4] ftrace: Add events for tracing timer interrupts Date: Wed, 08 Sep 2010 14:38:23 +0200 Message-ID: <1283949503.23762.9.camel@laptop> References: <1283948964-6418-1-git-send-email-jblunck@suse.de> <1283948964-6418-2-git-send-email-jblunck@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Cc: Linux-Kernel Mailinglist , linux-rt-users@vger.kernel.org, Sven-Thorsten Dietrich , Michael Galbraith To: Jan Blunck Return-path: Received: from casper.infradead.org ([85.118.1.10]:48003 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753697Ab0IHMi2 convert rfc822-to-8bit (ORCPT ); Wed, 8 Sep 2010 08:38:28 -0400 In-Reply-To: <1283948964-6418-2-git-send-email-jblunck@suse.de> Sender: linux-rt-users-owner@vger.kernel.org List-ID: On Wed, 2010-09-08 at 14:29 +0200, Jan Blunck wrote: > Trace the execution of the timer interrupt. I did not find an argument that > makes any sense so traces look like this: > > -0 [000] 181019.693546: timerirq_enter: unused=1 > -0 [000] 181019.693553: timerirq_exit: unused=1 So what's wrong with the normal IRQ enter/exit tracepoints?