Messages in this thread | | | From | Vaibhav Nagarnaik <> | Date | Wed, 6 Jul 2011 14:50:11 -0700 | Subject | Re: [PATCH v3] trace: Add x86 irq vector entry/exit tracepoints |
| |
On Tue, Jun 21, 2011 at 11:45 AM, Vaibhav Nagarnaik <vnagarnaik@google.com> wrote: > From: Jiaying Zhang <jiayingz@google.com> > > The current interrupt trace of irq_handler_entry and irq_handler_exit > give traces of when an interrupt is handled. They provide good data > about when the system is running in kernel space and how it affects the > currently running applications. > > Apart from this, they are IRQ vectors which trigger the system into > kernel space. Tracing such events gives us the trace of where the system > is spending its time. We want to know which cores are handling > interrupts and how they are affecting other processes in the system. > Also, the trace provides information about when the cores are idle and > which interrupts are changing that state. > > The following patch adds the event definition and trace instrumentation > for interrupt vectors. A lookup table is provided to print out readable > IRQ vector names. Apart from the IRQ vectors handled in the generic > kernel code, some x86 specific IRQ vectors are also traced. The lookup > table can be extended by adding other arch-specific IRQ vectors. > > Changelog: > v2-v3 > * Move the irq_vector_{entry|exit} tracepoints back under irq/ sub > folder > * Trace the common IRQs in generic kernel code so that all archs can > benefit. > > v1-v2 > * Move the irq_vector_{entry|exit} tracepoints under irq_vectors/ sub > folder > > Signed-off-by: Vaibhav Nagarnaik <vnagarnaik@google.com>
Hi All
Can you please take a look at this patch? Does it cover all the generic IRQ handlers so they are traced?
Thanks
Vaibhav Nagarnaik -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |