linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vaibhav Nagarnaik <vnagarnaik@google.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Steven Rostedt <rostedt@goodmis.org>,
	Michael Rubin <mrubin@google.com>,
	David Sharp <dhsharp@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] trace,x86: Add tracepoint to x86 timer interrupt handler
Date: Wed, 21 Sep 2011 11:20:51 -0700	[thread overview]
Message-ID: <CAL26m8JH7CyEdYUXtiC8fOmtSzeteFez2h-aWqJu06Lo77npAQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1109211053430.2723@ionos>

On Wed, Sep 21, 2011 at 2:01 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Fri, 29 Jul 2011, Vaibhav Nagarnaik wrote:
>
>> The x86 timer interrupt handler is the only handler not traced in the
>> irq/irq_handler_{entry|exit} trace events.
>
> Nonsense. The timer irq (irq0) comes via the genirq interrupt handling
> and not via a special vector. So it's traced already.
>

Thanks for pointing it out, I confused the PIT/HPET for the local timer
vector.

Could you also take a look at the patches that add tracing for traps?
https://lkml.org/lkml/2011/5/3/455
https://lkml.org/lkml/2011/5/3/456



Vaibhav Nagarnaik

  reply	other threads:[~2011-09-21 18:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 23:59 [PATCH 0/2] Add tracepoints to trace all x86 system IRQs Vaibhav Nagarnaik
2011-07-29 23:59 ` [PATCH 1/2] trace,x86: Add tracepoint to x86 timer interrupt handler Vaibhav Nagarnaik
2011-09-21  9:01   ` Thomas Gleixner
2011-09-21 18:20     ` Vaibhav Nagarnaik [this message]
2011-07-29 23:59 ` [PATCH 2/2] trace,x86: Add x86 irq vector entry/exit tracepoints Vaibhav Nagarnaik
2011-12-12 21:52   ` Seiji Aguchi
2011-12-13 19:26     ` Frederic Weisbecker
2011-12-14  8:18       ` Ingo Molnar
2011-12-14 14:47         ` Frederic Weisbecker
2011-12-14 16:19           ` Vaibhav Nagarnaik
2011-12-14 15:09       ` Seiji Aguchi
2011-12-14 16:34         ` Frederic Weisbecker
2011-12-14 16:37           ` Steven Rostedt
2011-12-14 17:46           ` Seiji Aguchi
2011-12-14 18:09             ` Steven Rostedt
2011-12-15  2:23               ` Seiji Aguchi
2012-02-03 15:40           ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAL26m8JH7CyEdYUXtiC8fOmtSzeteFez2h-aWqJu06Lo77npAQ@mail.gmail.com \
    --to=vnagarnaik@google.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dhsharp@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mrubin@google.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).