linux-kernel - Re: [PATCH v4 00/16] perf, persistent: Add 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]

Message-ID: <20140508182344.GG12548@pd.tnic>
Date:	Thu, 8 May 2014 20:23:44 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Robert Richter <rric@...nel.org>
Cc:	Jean Pihet <jean.pihet@...aro.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Jiri Olsa <jolsa@...hat.com>, linux-kernel@...r.kernel.org,
	Tomasz Nowicki <tomasz.nowicki@...aro.org>
Subject: Re: [PATCH v4 00/16] perf, persistent: Add persistent events

On Wed, May 07, 2014 at 06:44:07PM +0200, Robert Richter wrote:
> With transparently I mean that the process even does not know that the
> same event is already running by another process. The kernel detects
> this and maps the request to that event and buffer. Of course the
> event's buffer must be at least readonly to be shared for this.

Yes.

> This could be a mechanism to connect to persistent events. The kernel
> detects by type and attr that the requested event is already running
> persistent and maps to it.
> 
> But at the moment persistent events can only be shared using
> 
>  attr.type = PERF_TYPE_PERSISTENT
>  attr.config = id
> 
> So the above is more an alternative to connect to persistent events
> and the question is, which one to use. Presumable the easiest first,
> which is the current implementation.

Well, there is no trivial way to share event buffers if they're not
read-only AFAICT.

But in questions like this, we always have to step one step back and ask
ourselves: what are the use cases for shared events and after we have
enumerated them, to design the kernel side so that it supports them.

So, do we want anything else besides shared, read-only events?

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/