From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755625Ab1G1MIU (ORCPT ); Thu, 28 Jul 2011 08:08:20 -0400 Received: from casper.infradead.org ([85.118.1.10]:44697 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755571Ab1G1MIO (ORCPT ); Thu, 28 Jul 2011 08:08:14 -0400 Subject: Re: [PATCH v2 3/6] trace: Add tracepoints to IRQ work run handler From: Peter Zijlstra To: Vaibhav Nagarnaik Cc: Frederic Weisbecker , Thomas Gleixner , Ingo Molnar , Steven Rostedt , Michael Rubin , David Sharp , linux-kernel@vger.kernel.org, x86@kernel.org In-Reply-To: <1311793038-15155-4-git-send-email-vnagarnaik@google.com> References: <1310679495-29104-1-git-send-email-vnagarnaik@google.com> <1311793038-15155-4-git-send-email-vnagarnaik@google.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 28 Jul 2011 14:12:51 +0200 Message-ID: <1311855171.2617.170.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2011-07-27 at 11:57 -0700, Vaibhav Nagarnaik wrote: > @@ -122,6 +123,7 @@ void irq_work_run(void) > { > struct irq_work *list; > > + trace_irq_work_run_entry(0); > if (this_cpu_read(irq_work_list) == NULL) > return; > > @@ -149,6 +151,7 @@ void irq_work_run(void) > next_flags(NULL, IRQ_WORK_BUSY), > NULL); > } > + trace_irq_work_run_exit(0); > } > EXPORT_SYMBOL_GPL(irq_work_run); So what happens when we call irq_work_run() from the timer interrupt?