From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758525AbYBBHAt (ORCPT ); Sat, 2 Feb 2008 02:00:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750810AbYBBHAj (ORCPT ); Sat, 2 Feb 2008 02:00:39 -0500 Received: from ms-smtp-03.nyroc.rr.com ([24.24.2.57]:57364 "EHLO ms-smtp-03.nyroc.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750764AbYBBHAi (ORCPT ); Sat, 2 Feb 2008 02:00:38 -0500 Date: Sat, 2 Feb 2008 02:00:25 -0500 (EST) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Mathieu Desnoyers cc: LKML , Ingo Molnar , Linus Torvalds , Andrew Morton , Peter Zijlstra , Christoph Hellwig , Gregory Haskins , Arnaldo Carvalho de Melo , Thomas Gleixner , Tim Bird , Sam Ravnborg , "Frank Ch. Eigler" , Jan Kiszka , John Stultz , Arjan van de Ven , Steven Rostedt Subject: Re: [PATCH 21/23 -v8] Add markers to various events In-Reply-To: <20080131120605.GA8493@Krystal> Message-ID: References: <20080130210357.927754294@goodmis.org> <20080130210528.149582393@goodmis.org> <20080131120605.GA8493@Krystal> 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 5B On Thu, 31 Jan 2008, Mathieu Desnoyers wrote: > * Steven Rostedt (rostedt@goodmis.org) wrote: > > This patch adds markers to various events in the kernel. > > (interrupts, task activation and hrtimers) > > > > Hi Steven, > > I would propose the following standard for IRQ handler markers: > > trace_mark(kernel_irq_entry, "irq_id %u kernel_mode %u", irq, > (regs)?(!user_mode(regs)):(1)); Are you saying that two markers with the same name is ok? That would be great if that is true. > .... > trace_mark(kernel_irq_exit, MARK_NOARGS); My patches don't use this (yet) so I'm leaving out adding markers that are not used. I'm not disagreeing with adding these, it's just that a patch series should only add markers that are actually used. > > So we can know the elaspsed time in irq handlers and whether they are > nested on user of kernel code. > > The same for traps : > > trace_mark(kernel_arch_trap_entry, "trap_id %d ip #p%ld", trapnr, > instruction_pointer(regs)); > > Where we know the trap number and the instruction pointer that caused > the trap. Here again, we should put a : > > trace_mark(kernel_arch_trap_exit, MARK_NOARGS); > > At the end of the trap handlers. > > It makes automatic analysis _much_ easier than trying to gather each and > every handler instrumentation which would have a different name... > -- Steve