linux-kernel - Re: [RFC 0/2] apic: tracing IPI events

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 6 Aug 2010 13:46:11 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	mingo@...e.hu, rostedt@...dmis.org, yhlu.kernel@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/2] apic: tracing IPI events

On Fri, Aug 06, 2010 at 01:26:36PM +0200, Andi Kleen wrote:
> Jiri Olsa <jolsa@...hat.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@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/