linux-kernel - Re: [PATCH 5/6] perf_counter: add more context information

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1239050799.4557.24.camel@laptop>
Date:	Mon, 06 Apr 2009 22:46:39 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Corey Ashford <cjashfor@...ux.vnet.ibm.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/6] perf_counter: add more context information

On Mon, 2009-04-06 at 13:16 -0700, Corey Ashford wrote:

> >> One downside of this approach is that you if you specify "no header" 
> >> (currently not possible, but maybe later?), you will not be able to get 
> >> the level bits.
> > 
> > Would this be desirable? 

> I think it would.  For one use case I'm working on right now, simple 
> profiling, all I need are ip's.  If I could omit the header, that would 
> reduce the frequency of sigio's by a factor of three, and make it faster 
> to read up the ip's when the SIGIO's occur.

Self-profiling?

So you're interested in getting the smallest possible record size, that
would still be 2 u64, right? Otherwise you don't get the IP context that
started this.


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