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]
Date:	Wed, 19 Dec 2012 13:55:43 -0800
From:	Andi Kleen <andi@...stfloor.org>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	linux-kernel@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 3/3] perf tool: Add non arch events for SandyBridge microarchitecture

Jiri Olsa <jolsa@...hat.com> writes:

> Adding non architectural event aliases for Sandy Bridge
> microarchitecture.

"SandyBridge" is not necessarily unique. There are flavours
of sandy bridge with slightly different events (e.g. in offcore)
Also there's uncores too, which are very different between
different SandyBridges.

I would merge all these little files into a single file.
I don't think anyone wants hundreds of new files for this, 
if you do it for multiple CPUs.

Besides it would waste insane amounts of space on most file systems
without tail packing -- each of your little files takes 4K plus an inode
and directory entry.

Intel normally uses a spreadsheet CSV format.

Best would be probably to just teach perf about reading one of those
standard formats, then they could be just downloaded somewhere.
I have some python scripts that do it as a wrapper.

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

Powered by blists - more mailing lists