linux-kernel - Re: regarding [PATCH] Add libpfm4 support (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: <1312806326.10488.30.camel@twins>
Date:	Mon, 08 Aug 2011 14:25:25 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	linux-kernel@...r.kernel.org, Arun Sharma <asharma@...com>
Subject: Re: regarding [PATCH] Add libpfm4 support (v3)

On Mon, 2011-08-08 at 14:04 +0200, Jiri Olsa wrote:
> hi,
> 
> any chance of getting this included?
> http://article.gmane.org/gmane.comp.linux.perfmon2.devel/2912
> http://article.gmane.org/gmane.comp.linux.perfmon2.devel/2912/raw
> 
> it needs just some little changes to fit to current tip tree

While I don't mind extending the current way to input events I don't
think using libpfm4 for it is desired.

One of the ideas that has been floating about is to provide a format
file in the sysfs representation of the pmu. This format file would
describe the config space. The tool would parse this and use it to
provide better input capabilities.

This is not an easy task however, since the format syntax needs to be
capable enough to describe all the various config muck we need to
support, think for example of the P4 mess.

For Intel/AMD (excluding P4) its mostly simple, with Intel having a
slightly harder time for the offcore bits.

As to the various arch event lists, again that is not something we need
a whole library for, parsing those text files isn't hard. Maintaining
the various arch event lists in a sane format is the 'hard' part and is
something I think we should push to the vendors, because they're
basically the only ones capable.

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