[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 03/15] xen/tools: tracing: several improvements on IRQs tracing
On 01/06/17 18:33, Dario Faggioli wrote: > More specifically: > - the handling of the TRC_HW_IRQ_HANDLED is fixed, both in > xentrace_format and in xenalyze; > - simple events for recording when we enter and exit the > do_IRQ function, as well as when we deal with a guest > IRQ, are added; > - tracing of IRQs handled with direct vectors is also > added. > > With all the above, a trace will now look like this (using > xenalyze): > > 0.001299072 .x- d32768v5 irq_enter, irq 80000000 > 0.001299072 .x- d32768v5 irq_direct, vec fa, handler = 0xffff82d08026d7e4 > 0.001300014 .x- d32768v5 raise_softirq nr 0 > 0.001300487 .x- d32768v5 irq_exit irq 80000000, in_irq = 0 > > Or like this: > > 0.049437892 -|- d32767v12 irq_enter, irq 4 > 0.049437892 -|- d32767v12 irq_handled irq 4, 85428 cycles > 0.049474336 -|- d32767v12 irq_exit irq 4, status = 0x0, in_irq = 0 > > Making it much easier to figure out when interrupt > processing start, what it does and when it ends. > > Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Generally looks good to me. I mostly agree with the commentary as well. -George _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |