linux-kernel - RE: [PATCH/RFC v2 0/3] Human readable platform-specific performance event support

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:	Thu, 28 Jan 2010 13:13:35 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Tomasz Fujak <t.fujak@...sung.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	acme@...hat.com, jamie.iles@...ochip.com, will.deacon@....com,
	jpihet@...sta.com, mingo@...e.hu,
	Pawel Osciak <p.osciak@...sung.com>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	kyungmin.park@...sung.com,
	Michal Nazarewicz <m.nazarewicz@...sung.com>
Subject: RE: [PATCH/RFC v2 0/3] Human readable platform-specific
 performance event support

On Thu, 2010-01-28 at 12:57 +0100, Tomasz Fujak wrote:

please educate your MUA to wrap lines at ~80.

> Apparently I did not comprehend your attitude towards the events'
> description being exported from the kernel.
> There's been a lengthy discussion which ended in a conclusion that the
> platform detection is a complicated task.

If its really that complicated export a pmu identifier someplace.

The fact is, the kernel simply doesn't use this list, we have perf in
kernel so that resource scheduling and isolation can be done, for that
we need to know how to program the hardware and we need to know about
scheduling constraints, we do not need exhaustive lists of possible
events, let alone descriptive text for them, in the kernel.



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