lkml.org 
[lkml]   [2010]   [Aug]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 0/2] apic: tracing IPI events
On Fri, Aug 06, 2010 at 01:26:36PM +0200, Andi Kleen wrote:
> Jiri Olsa <jolsa@redhat.com> writes:
> >
> > please let me know what you think
>
> You forgot to state why you want it?
>
> In generall the only case that should happen anytime commonly is mask,
> the others only for obscure uncommon paths.
>
> However there is already accounting for it in /proc/interrupts
> that can be easily sampled. Does adding additional tracing really give
> any value?

As I was asked to do that for other guys, I'm not completely sure.
Anyway the reason I got was, that while debuging crash it seemed
some IPIs might got lost.

Also it'd be probably used as a tracepoint itself via additional code,
than by ring buffer tracing.

I'll check if I can get more justifing info..

jirka

>
> -Andi
> --
> ak@linux.intel.com -- Speaking for myself only.


\
 
 \ /
  Last update: 2010-08-06 13:49    [W:0.069 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site