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

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: <1315423726.11101.27.camel@twins>
Date:	Wed, 07 Sep 2011 21:28:46 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	linux-kernel@...r.kernel.org, acme@...hat.com, mingo@...e.hu,
	dsahern@...il.com
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v3)

On Wed, 2011-09-07 at 14:55 +0200, Stephane Eranian wrote:
> On Wed, Sep 7, 2011 at 10:12 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> > On Tue, 2011-09-06 at 22:46 +0200, Stephane Eranian wrote:
> >> +static const char *topo_fmt[] = {
> >> +       "/sys/devices/system/cpu/cpu%d/topology/core_siblings_list",
> >> +       "/sys/devices/system/cpu/cpu%d/topology/thread_siblings_list",
> >> +       NULL
> >> +};
> >
> > No nodes?
> >
> To record what information? core/thread siblings or memory stuff?

Dunno really,.. but nodes are part of the topology and with people
interested in all this uncore business it might make sense to have that.
Maybe even record the node-distance table so you can reconstruct the
interconnect topology.


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