From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jonatan Corbet <corbet@lwn.net>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: 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: [PATCH v2 0/3] admin-guide: extend perf-security with resource control, data categories and privileged users
Date: Thu, 7 Feb 2019 16:23:22 +0300 [thread overview]
Message-ID: <fd896eec-7833-f23a-ad2f-95005dca5fff@linux.intel.com> (raw)
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;
---
Alexey Budankov (4):
perf-security: document perf_events/Perf resource control
perf-security: document collected perf_events/Perf data categories
perf-security: elaborate on perf_events/Perf privileged users
perf-security: wrap paragraphs on 72 columns
Documentation/admin-guide/perf-security.rst | 247 +++++++++++++++-----
1 file changed, 187 insertions(+), 60 deletions(-)
---
Changes in v2:
- addressed comments for v1
- added fourth patch implementing 72 columns paragraph width
---
[1] https://marc.info/?l=linux-kernel&m=153736008310781&w=2
[2] https://lkml.org/lkml/2018/5/21/156
[3] https://lkml.org/lkml/2018/11/27/604
[4] http://man7.org/linux/man-pages/man2/perf_event_open.2.html
next reply other threads:[~2019-02-07 13:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 13:23 Alexey Budankov [this message]
2019-02-07 13:29 ` [PATCH v2 1/4] perf-security: document perf_events/Perf resource control Alexey Budankov
2019-02-10 22:34 ` Thomas Gleixner
2019-02-11 12:46 ` Alexey Budankov
2019-02-11 14:15 ` Thomas Gleixner
2019-02-11 14:22 ` Alexey Budankov
2019-02-07 13:30 ` [PATCH v2 2/4] perf-security: document collected perf_events/Perf data categories Alexey Budankov
2019-02-07 13:31 ` [PATCH v2 3/4] perf-security: elaborate on perf_events/Perf privileged users Alexey Budankov
2019-02-07 13:32 ` [PATCH v2 4/4] perf-security: wrap paragraphs on 72 columns Alexey Budankov
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=fd896eec-7833-f23a-ad2f-95005dca5fff@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@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.