From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753282AbaEFSyH (ORCPT ); Tue, 6 May 2014 14:54:07 -0400 Received: from mail.skyhub.de ([78.46.96.112]:41347 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751255AbaEFSyE (ORCPT ); Tue, 6 May 2014 14:54:04 -0400 Date: Tue, 6 May 2014 20:53:59 +0200 From: Borislav Petkov To: Robert Richter Cc: Jean Pihet , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Jiri Olsa , linux-kernel@vger.kernel.org, Tomasz Nowicki Subject: Re: [PATCH v4 00/16] perf, persistent: Add persistent events Message-ID: <20140506185359.GE25013@pd.tnic> References: <1396883078-25320-1-git-send-email-jean.pihet@linaro.org> <20140506123907.GV32718@rric.localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20140506123907.GV32718@rric.localhost> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 06, 2014 at 02:39:07PM +0200, Robert Richter wrote: > Events could also be shared transparently. This means, if there is > already an event running with the same attr, it could be reused. Not > sure if this makes sense much and is also feasible. Most events are > opened with writable buffers and thus can not be shared anyway. Well, this is simple: sharing events implicitly says they're read-only - you can't share them otherwise. If you want the buffers to be writable, then the events cannot be shared. I think this is nicely simple. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --