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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87bp9gc783.fsf@basil.nowhere.org>
Date:	Fri, 06 Aug 2010 13:26:36 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Jiri Olsa <jolsa@...hat.com>
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

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?

-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/