Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git...

Pull perf/core improvements and fixes from Arnaldo Carvalho de Melo:

User visible changes:

 - Rename the "colors.code" ~/.perfconfig variable to "colors.jump_arrows",
   as it controls just the that UI element in the annotate browser (Taeung Song)

 - Avoid trying to read ELF symtabs from device files, noticed while doing
   memory profiling work (Jiri Olsa)

 - Improve context detection when offering options in the hists browser,
   i.e.  some options don't make sense when the browser is not working with
   a perf.data file ('perf top' mode), only in 'perf report' mode, like
   scripting (Namhyung Kim)

Infrastructure changes:

 - Elliminate duplication in the hists browser filter functions, getting the
   common part into a function that receives callbacks for filtering by
   DSO, thread, etc. (Namhyung Kim)

 - Fix misleadingly indented assignment, found using
   gcc6 -Wmisleading-indentation (Markus Trippelsdorf)

 - Handle LLVM relocation oddities in libbpf, introducing a 'perf test' that
   detects such problems and then fixing the problem, so that the test now
   passes (Wang Nan)

 - More improvements to the build infrastructure to allow reusing the
   feature detection facilities (Wang Nan)

 - Auto initialize the globals needed by cpu__max_{cpu,node}() routines
   (Arnaldo Carvalho de Melo)

Documentation changes:

 - Document the perf sysctls in Documentation/sysctl/kernel.txt (Ben Hutchings)

 - Document a bunch more ~/.perfconfig knobs (Taeung Song)

Signed-off-by: Arnaldo Carvalho de Melo <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>

diff --combined Documentation/sysctl/kernel.txt
index a93b414672a71ac6fa9bac1e848215804bde139c,c803e7300f0b13c917928a8ffa4bce1d6a2089a4..f886fbb1ad05d78ecda7c8a3289528ce9613665a
--- 1/Documentation/sysctl/kernel.txt
--- 2/Documentation/sysctl/kernel.txt
+++ b/Documentation/sysctl/kernel.txt
@@@ -58,6 -58,8 +58,8 @@@ show up in /proc/sys/kernel
  - panic_on_stackoverflow
  - panic_on_unrecovered_nmi
  - panic_on_warn
+ - perf_cpu_time_max_percent
+ - perf_event_paranoid
  - pid_max
  - powersave-nap               [ PPC only ]
  - printk
@@@ -639,6 -641,17 +641,17 @@@ allowed to execute
  
  ==============================================================
  
+ perf_event_paranoid:
+ 
+ Controls use of the performance events system by unprivileged
+ users (without CAP_SYS_ADMIN).  The default value is 1.
+ 
+  -1: Allow use of (almost) all events by all users
+ >=0: Disallow raw tracepoint access by users without CAP_IOC_LOCK
+ >=1: Disallow CPU event access by users without CAP_SYS_ADMIN
+ >=2: Disallow kernel profiling by users without CAP_SYS_ADMIN
+ 
+ ==============================================================
  
  pid_max:
  
@@@ -825,13 -838,14 +838,13 @@@ via the /proc/sys interface
         Each write syscall must fully contain the sysctl value to be
         written, and multiple writes on the same sysctl file descriptor
         will rewrite the sysctl value, regardless of file position.
 -   0 - (default) Same behavior as above, but warn about processes that
 -       perform writes to a sysctl file descriptor when the file position
 -       is not 0.
 -   1 - Respect file position when writing sysctl strings. Multiple writes
 -       will append to the sysctl value buffer. Anything past the max length
 -       of the sysctl value buffer will be ignored. Writes to numeric sysctl
 -       entries must always be at file position 0 and the value must be
 -       fully contained in the buffer sent in the write syscall.
 +   0 - Same behavior as above, but warn about processes that perform writes
 +       to a sysctl file descriptor when the file position is not 0.
 +   1 - (default) Respect file position when writing sysctl strings. Multiple
 +       writes will append to the sysctl value buffer. Anything past the max
 +       length of the sysctl value buffer will be ignored. Writes to numeric
 +       sysctl entries must always be at file position 0 and the value must
 +       be fully contained in the buffer sent in the write syscall.
  
  ==============================================================