From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jann Horn <jannh@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] admin-guide: extend perf-security with resource control, data categories and privileged users
Date: Mon, 18 Feb 2019 11:56:30 +0300 [thread overview]
Message-ID: <c26bd0a2-f0a3-47d4-0ff8-620a677d7a91@linux.intel.com> (raw)
In-Reply-To: <20190217161428.6b43608a@lwn.net>
On 18.02.2019 2:14, Jonathan Corbet wrote:
> On Mon, 11 Feb 2019 16:32:33 +0300
> Alexey Budankov <alexey.budankov@linux.intel.com> wrote:
>
>> The patch set extends the first version of perf-security.rst documentation
>> file [1], [2], [3] with the following topics:
>>
>> 1) perf_events/Perf resource limits and control management that describes
>> RLIMIT_NOFILE and perf_event_mlock_kb settings for processes conducting
>> performance monitoring;
>>
>> 2) categories of system and performance data that can be captured by
>> perf_events/Perf with explicit designation of process sensitive data;
>>
>> 3) possible steps to create perf_event/Perf privileged users groups for
>> the current implementations of perf_events syscall API [4] and Perf tool;
>
> I've applied the set, thanks.
Thanks a lot Jon!
~Alexey
>
> jon
>
prev parent reply other threads:[~2019-02-18 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 13:32 [PATCH v3 0/3] admin-guide: extend perf-security with resource control, data categories and privileged users Alexey Budankov
2019-02-11 13:42 ` [PATCH v3 1/4] perf-security: document perf_events/Perf resource control Alexey Budankov
2019-02-11 13:43 ` [PATCH v3 2/4] perf-security: document collected perf_events/Perf data categories Alexey Budankov
2019-02-11 13:44 ` [PATCH v3 3/4] perf-security: elaborate on perf_events/Perf privileged users Alexey Budankov
2019-02-11 14:58 ` [PATCH v3 4/4] perf-security: wrap paragraphs on 72 columns Alexey Budankov
2019-02-17 23:14 ` [PATCH v3 0/3] admin-guide: extend perf-security with resource control, data categories and privileged users Jonathan Corbet
2019-02-18 8:56 ` Alexey Budankov [this message]
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=c26bd0a2-f0a3-47d4-0ff8-620a677d7a91@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=corbet@lwn.net \
--cc=jannh@google.com \
--cc=jolsa@redhat.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tvrtko.ursulin@linux.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