linux-kernel - Re: [PATCH] perf: make perf.data more self-descriptive (v5)

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

Message-ID: <35021.1316815985@turing-police.cc.vt.edu>
Date:	Fri, 23 Sep 2011 18:13:05 -0400
From:	Valdis.Kletnieks@...edu
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Stephane Eranian <eranian@...gle.com>,
	linux-kernel@...r.kernel.org, acme@...hat.com,
	peterz@...radead.org, mingo@...e.hu, dsahern@...il.com,
	robert.richter@....com, ak@...ux.intel.com
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v5)

On Thu, Sep 22, 2011 at 3:31 PM, Stephane Eranian <eranian@...gle.com> wrote:
> # CPU0 sibling cores  : 0-3
> # CPU0 sibling threads: 0
> # CPU1 sibling cores  : 0-3
> # CPU1 sibling threads: 1
> # CPU2 sibling cores  : 0-3
> # CPU2 sibling threads: 2

On Fri, 23 Sep 2011 11:03:20 +0300, Pekka Enberg said:
> Well, sure but it blocks rest of the interesting information too. It seems to me
> that the CPU information could be truncated to some sane limit by default and
> introduce a command line option for users that really want to see all of it.

Too bad there's probably no easy way to provide an iterator/metafunction that
describes the CPUs, so it could output 

"for n in 0..4095 cpu[n] looks like this: 
   CPU_n sibling cores: round(n,4)..round(n,4)+3
   CPU_n sibling threads: n...

Content of type "application/pgp-signature" skipped