mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jann Horn <jannh@google.com>
Cc: Andi Kleen <ak@linux.intel.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	tursulin@ursulin.net, kernel list <linux-kernel@vger.kernel.org>,
	tvrtko.ursulin@linux.intel.com,
	Peter Zijlstra <peterz@infradead.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	"H . Peter Anvin" <hpa@zytor.com>,
	acme@kernel.org, alexander.shishkin@linux.intel.com,
	jolsa@redhat.com, namhyung@kernel.org, maddy@linux.vnet.ibm.com,
	Kees Cook <keescook@chromium.org>
Subject: Re: [RFC 0/5] perf: Per PMU access controls (paranoid setting)
Date: Mon, 1 Oct 2018 09:25:42 +0300	[thread overview]
Message-ID: <22155f49-2f57-73b8-6e89-ddd8a127967b@linux.intel.com> (raw)
In-Reply-To: <20180928212757.GE32651@tassilo.jf.intel.com>

Hello Jann,

> On Fri, Sep 28, 2018 at 11:22:37PM +0200, Jann Horn wrote:
<SNIP>
>>
>> <blasphemy>
>> Is that true? IIRC if you want to use the perf tools after a kernel
>> update, you have to install a new version of perf anyway, no?

There are usages in production where perf_event_open() syscall 
accompanied with read(), mmap() etc. is embedded into application 
on per-thread basis and is used for self monitoring and dynamic 
execution tuning.

There are also other Perf tools around that, for example, are 
statically linked and then used as on Linux as on Android.

Backward compatibility does matter in these cases.

Thanks,
Alexey

  reply	other threads:[~2018-10-01  6:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 12:27 Tvrtko Ursulin
2018-09-19 12:27 ` [RFC 1/5] perf: Move some access checks later in perf_event_open Tvrtko Ursulin
2018-09-19 12:27 ` [RFC 2/5] perf: Pass pmu pointer to perf_paranoid_* helpers Tvrtko Ursulin
2018-09-19 12:27 ` [RFC 3/5] perf: Allow per PMU access control Tvrtko Ursulin
2018-09-27 20:15   ` Andi Kleen
2018-09-28  8:57     ` Tvrtko Ursulin
2018-09-19 12:27 ` [RFC 4/5] perf Documentation: Document the per PMU perf_event_paranoid interface Tvrtko Ursulin
2018-09-19 12:27 ` [RFC 5/5] tools/perf: Add support for per-PMU access control Tvrtko Ursulin
2018-09-28 10:26 ` [RFC 0/5] perf: Per PMU access controls (paranoid setting) Thomas Gleixner
2018-09-28 13:22   ` Tvrtko Ursulin
2018-09-28 14:02     ` Thomas Gleixner
2018-09-28 14:56       ` Tvrtko Ursulin
2018-09-28 15:23         ` Thomas Gleixner
2018-09-28 15:45       ` Alexey Budankov
2018-09-28 18:20         ` Thomas Gleixner
2018-09-28 20:45           ` Andi Kleen
2018-09-29  6:19             ` Thomas Gleixner
2018-10-01  6:25           ` Alexey Budankov
2018-09-28 15:12     ` Jann Horn
2018-09-28 22:02       ` Jann Horn
2018-10-01  6:27         ` Alexey Budankov
2018-09-28 16:41   ` Mark Rutland
2018-09-28 17:23     ` Andi Kleen
2018-09-28 17:40       ` Mark Rutland
2018-09-28 20:49         ` Andi Kleen
2018-09-28 20:54           ` Jann Horn
2018-09-28 20:59             ` Andi Kleen
2018-09-28 21:22               ` Jann Horn
2018-09-28 21:27                 ` Andi Kleen
2018-10-01  6:25                   ` Alexey Budankov [this message]
2018-10-01 16:11                     ` Thomas Gleixner
2018-10-01 16:15                       ` Jann Horn
2018-10-01 20:51                       ` Alexey Budankov
2018-10-02  6:40                         ` Thomas Gleixner
2018-10-02 11:44                           ` Alexey Budankov
2018-10-03 17:01                         ` Jann Horn
2018-10-04 17:11                           ` Alexey Budankov
2018-09-29  6:30               ` Thomas Gleixner

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=22155f49-2f57-73b8-6e89-ddd8a127967b@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=hpa@zytor.com \
    --cc=jannh@google.com \
    --cc=jolsa@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=mark.rutland@arm.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=tursulin@ursulin.net \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=x86@kernel.org \
    /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
Powered by JetHome