From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751621Ab1GMSSo (ORCPT ); Wed, 13 Jul 2011 14:18:44 -0400 Received: from smtp-out.google.com ([216.239.44.51]:32382 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750706Ab1GMSSn convert rfc822-to-8bit (ORCPT ); Wed, 13 Jul 2011 14:18:43 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type: content-transfer-encoding:x-system-of-record; b=XEuiqWpfEudrgaZd/Bdegb6nQ+y0wdBgeZmQa5XXROcXQ5aXdysz+D4Rcgadyz43q vTh7Bx1HttVU8z97pZztQ== MIME-Version: 1.0 In-Reply-To: <20110713141129.GG9201@somewhere> References: <1306877298-31713-1-git-send-email-vnagarnaik@google.com> <1308681903-12840-1-git-send-email-vnagarnaik@google.com> <20110707233453.GE21115@somewhere> <20110711155404.GB4109@somewhere.redhat.com> <20110712180859.GC9201@somewhere> <20110713141129.GG9201@somewhere> From: Vaibhav Nagarnaik Date: Wed, 13 Jul 2011 11:18:10 -0700 Message-ID: Subject: Re: [PATCH v3] trace: Add x86 irq vector entry/exit tracepoints To: Frederic Weisbecker Cc: David Sharp , Thomas Gleixner , Ingo Molnar , Steven Rostedt , Michael Rubin , linux-kernel@vger.kernel.org, x86@kernel.org, Jiaying Zhang Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 13, 2011 at 7:11 AM, Frederic Weisbecker wrote: > On Tue, Jul 12, 2011 at 03:08:48PM -0700, Vaibhav Nagarnaik wrote: >> Breaking this patch up in different small ones makes sense. Can you >> comment on this proposal for the following trace events? >> >> For tracepoints in generic IRQ handlers: >> 1. trace_timer_vector - takes an enum for BROADCAST, HRTIMER, ONESHOT, >>    PERIODIC and NOHZ. > > Have you read my previous email entirely? > > Where I explained we shouldn't use that vector naming outside of low > level archs, and that those enums break tracing granularity? > I was arguing for an enum for this since it is a single contained trace event for all timers. But you are right, since I'm breaking up the interrupts in different trace events already, timer interrupts should also have separate trace events for granularity. >> 2. trace_irq_work_vector - for IRQ_WORK_VECTOR > > trace_irq_work_run() should be enough. And people can add > trace_irq_work_queue() if they need to one day. > > >> 3. trace_reschedule_vector - for RESCHEDULE_IPI vector > > trace_reschedule_interrupt() > > >> 4. trace_call_function_vector - takes an enum for CALL_FUNCTION and >>    CALL_FUNCTION_SINGLE > > Two seperate tracepoints should be better. > > >> Another trace event for arch-specific IRQ vectors which don't have >> generic event handlers: >> 5. trace_platform_irq_vector - takes an enum, which is defined in >>    asm/irq.h for each platform. This is traced in arch-specific files >>    only. > > Yep. For this perhaps an enum can make sense. > > Thanks. > I will create and post the patch series soon. Thanks Vaibhav Nagarnaik