[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171003144222.fkwufhowb7lrqwi3@hirez.programming.kicks-ass.net>
Date: Tue, 3 Oct 2017 16:42:22 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc: Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
acme@...hat.com, kirill.shutemov@...ux.intel.com,
Borislav Petkov <bp@...en8.de>, rric@...nel.org
Subject: Re: [RFC PATCH 08/17] perf: Allow inheritance for detached events
On Tue, Sep 05, 2017 at 04:30:17PM +0300, Alexander Shishkin wrote:
> This enables inheritance for detached events. Unlike traditional events,
> these do not have parents: inheritance produces a new independent event
> with the same attribute. If the 'parent' event has a ring buffer, so will
> the new event. Considering the mlock accounting, this buffer allocation
> may fail, which in turn will fail the parent's fork, something to be
> aware of.
>
> This also effectively disables context cloning, because unlike the
> traditional events, these will each have its own ring buffer and
> context switch optimization can't work.
Right, so this thing is icky... as you know. More naming issues though,
what will you go and call those files.
Powered by blists - more mailing lists