Messages in this thread | | | Date | Sat, 28 May 2011 11:41:50 +0200 | From | Ingo Molnar <> | Subject | Re: [GIT PULL 0/5] perf/urgent fixes |
| |
* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> Hi Ingo, > > Please consider pulling from: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6 perf/urgent > > Regards, > > - Arnaldo > > Arnaldo Carvalho de Melo (4): > perf tools: Make sure kptr_restrict warnings fit 80 col terms > perf top: Remove unused macro > perf top: Handle kptr_restrict > perf top: Don't stop if no kernel symtab is found > > David Ahern (1): > perf events: initialize fd array to -1 instead of 0 > > tools/perf/builtin-record.c | 19 ++++++++----------- > tools/perf/builtin-report.c | 17 +++++++---------- > tools/perf/builtin-top.c | 37 ++++++++++++++++++++++++++++++------- > tools/perf/util/evsel.c | 10 ++++++++++ > 4 files changed, 55 insertions(+), 28 deletions(-)
Pulled, thanks a lot Arnaldo!
The various variations of kptr_restrict now work fine AFAICS - will send the fixes to Linus today.
One (very) small issue i noticed, if the user only samples user-space events then i still get the warning:
aldebaran:~> perf record -e cycles:upp sleep 1 WARNING: Kernel address maps (/proc/{kallsyms,modules}) are restricted,
although perf does not record any kernel samples so kptr_restrict is irrelevant in this case.
Ingo
| |