linux-kernel - Re: [rfc 3/3] perf, x86: P4 PMU -- export ABI part of event config to userspace

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, 24 Nov 2010 11:48:11 +0300
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>,
	ming.m.lin@...el.com, eranian@...gle.com
Subject: Re: [rfc 3/3] perf, x86: P4 PMU -- export ABI part of event config to userspace

On 11/24/10, Peter Zijlstra <peterz@...radead.org> wrote:
> On Wed, 2010-11-24 at 01:46 +0300, Cyrill Gorcunov wrote:
>> plain text document attachment (x86-perf-export-abi)
>> Due to tight 64 bit size of event config field (where we have to track
>> pretty lot of info during event lifetime) some bits are to be exported
>> via header into userspace.
>>
>> Signed-off-by: Cyrill Gorcunov <gorcunov@...nvz.org>
>> CC: Lin Ming <ming.m.lin@...el.com>
>> CC: Stephane Eranian <eranian@...gle.com>
>> CC: Peter Zijlstra <peterz@...radead.org>
>> ---
>>
>> Note that I don't like much the idea to export anything into userspace
>> but it seems there is no other choise. So there is a minimum which should
>> be exported.
>
>
> Could you say what exactly is exposed to userspace and why?

yes, we need two enums to be exported, because we use custom encoding,
which is described in first patch. peter i'll describe more detailed
in a couple of hours, ok?
>
--
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/