From: Peter Zijlstra <peterz@infradead.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] perf: Allow fine-grained PMU access control
Date: Fri, 19 Jan 2018 17:45:40 +0100 [thread overview]
Message-ID: <20180119164540.GT2228@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180118184007.1300-1-tvrtko.ursulin@linux.intel.com>
On Thu, Jan 18, 2018 at 06:40:07PM +0000, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> 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.
next prev parent reply other threads:[~2018-01-19 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 18:40 [RFC] perf: Allow fine-grained PMU access control Tvrtko Ursulin
2018-01-19 16:45 ` Peter Zijlstra [this message]
2018-01-19 17:10 ` [Intel-gfx] " Tvrtko Ursulin
2018-02-23 15:58 ` Tvrtko Ursulin
-- strict thread matches above, loose matches on Subject: below --
2018-05-21 9:25 Tvrtko Ursulin
2018-05-22 9:05 ` Peter Zijlstra
2018-05-22 9:29 ` Tvrtko Ursulin
2018-05-22 12:32 ` Peter Zijlstra
2018-05-22 13:01 ` Alexey Budankov
2018-05-22 17:19 ` Andi Kleen
2018-06-11 8:08 ` Tvrtko Ursulin
2018-06-18 8:06 ` Alexey Budankov
2018-05-22 16:15 ` Tvrtko Ursulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180119164540.GT2228@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=tursulin@ursulin.net \
--cc=tvrtko.ursulin@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox