linux-kernel - Re: [RFC PATCH 0/3] Perf persistent events

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:	Mon, 18 Mar 2013 09:46:38 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Namhyung Kim <namhyung@...nel.org>
Cc:	Borislav Petkov <bp@...en8.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Borislav Petkov <bp@...e.de>, Robert Richter <rric@...nel.org>
Subject: Re: [RFC PATCH 0/3] Perf persistent events

* Namhyung Kim <namhyung@...nel.org> wrote:

> So my question is how can an user know which persistent events are 
> available in her system?

I think we need VFS enumeration for that: directories give a high level a 
structure (allowing things like per user contexts) while readdir will give 
list of specific persistent buffer contexts.

Sensible naming convention would be needed to make things easy to discover 
and list - and for active buffers to not be forgotten about.

cgroups or a new 'eventfs' filesystem would be an option.

Thanks,

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