From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf tools pt: Remove obsolete paragraph in intel-pt.c
Date: Wed, 9 Nov 2016 11:39:41 -0300 [thread overview]
Message-ID: <20161109143941.GH12125@kernel.org> (raw)
In-Reply-To: <344fddd4-718b-ecf3-75f0-585eda90df6f@intel.com>
Em Wed, Nov 09, 2016 at 04:01:12PM +0200, Adrian Hunter escreveu:
> On 09/11/16 15:59, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Nov 09, 2016 at 10:14:26AM -0300, Arnaldo Carvalho de Melo escreveu:
> >> Em Tue, Nov 08, 2016 at 04:11:00PM -0800, Andi Kleen escreveu:
> >>> From: Andi Kleen <ak@linux.intel.com>
> >>>
> >>> Since the unprivileged sched switch event was added in perf,
> >>> PT doesn't need need perf_event_paranoid=-1 anymore for
> >>> per cpu decoding. So remove the obsolete paragraph in
> >>> the documentation.
> >>
> >> Thanks for pointing that out, I'll do something slightly different tho,
> >> pointing out that from kernel X.Y.Z, when the unprivileged
> >> PERF_RECORD_SWITCH metadata event was introduced, this is no longer an
> >> issue, having to be considered only on older kernels.
> >
> > It ended up as:
> >
> > diff --git a/tools/perf/Documentation/intel-pt.txt b/tools/perf/Documentation/intel-pt.txt
> > index c6c8318e38a2..4d12db118476 100644
> > --- a/tools/perf/Documentation/intel-pt.txt
> > +++ b/tools/perf/Documentation/intel-pt.txt
> > @@ -546,6 +546,18 @@ mode by using the --per-thread option.
> > Privileged vs non-privileged users
> > ----------------------------------
> >
> > +The v4.2 kernel introduced support for a context switch metadata event,
> > +PERF_RECORD_SWITCH, which allows unprivileged users to see when their processes
> > +are scheduled out and in, just not by whom, which is left for the
> > +PERF_RECORD_SWITCH_CPU_WIDE, that is only accessible in system wide context,
> > +which in turn requires CAP_SYS_ADMIN.
> > +
> > +Please see the 45ac1403f564 ("perf: Add PERF_RECORD_SWITCH to indicate context
> > +switches") commit, that introduces these metadata events for further info.
> > +
> > +When working with kernels < v4.2, the following considerations must be taken,
> > +as the sched:sched_switch tracepoints will be used to receive such information:
> > +
> > Unless /proc/sys/kernel/perf_event_paranoid is set to -1, unprivileged users
> > have memory limits imposed upon them. That affects what buffer sizes they can
> > have as outlined above.
>
> Maybe put that last paragraph about memory limits above the new text.
Ok, as it is not affected by the new text, thanks.
- Arnaldo
next prev parent reply other threads:[~2016-11-09 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 0:11 [PATCH] perf tools pt: Remove obsolete paragraph in intel-pt.c Andi Kleen
2016-11-09 13:14 ` Arnaldo Carvalho de Melo
2016-11-09 13:59 ` Arnaldo Carvalho de Melo
2016-11-09 14:01 ` Adrian Hunter
2016-11-09 14:39 ` Arnaldo Carvalho de Melo [this message]
2016-11-09 14:44 ` Arnaldo Carvalho de Melo
2016-11-10 8:11 ` Adrian Hunter
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=20161109143941.GH12125@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.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 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.