From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756147AbeASQqE (ORCPT ); Fri, 19 Jan 2018 11:46:04 -0500 Received: from merlin.infradead.org ([205.233.59.134]:56608 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755983AbeASQpz (ORCPT ); Fri, 19 Jan 2018 11:45:55 -0500 Date: Fri, 19 Jan 2018 17:45:40 +0100 From: Peter Zijlstra To: Tvrtko Ursulin Cc: Intel-gfx@lists.freedesktop.org, Tvrtko Ursulin , Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin , Jiri Olsa , Namhyung Kim , linux-kernel@vger.kernel.org Subject: Re: [RFC] perf: Allow fine-grained PMU access control Message-ID: <20180119164540.GT2228@hirez.programming.kicks-ass.net> References: <20180118184007.1300-1-tvrtko.ursulin@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180118184007.1300-1-tvrtko.ursulin@linux.intel.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 18, 2018 at 06:40:07PM +0000, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > For situations where sysadmins might want to allow different level of > of access control for different PMUs, we start creating per-PMU > perf_event_paranoid controls in sysfs. You've completely and utterly failed to explain why.