* Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> wrote: > Em Thu, May 26, 2011 at 09:39:46PM +0200, Ingo Molnar escreveu: > > > > * tip-bot for Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> wrote: > > > > > Commit-ID: ec80fde746e3ccf93895d25ae1a7071c9af52585 > > > Gitweb: http://git.kernel.org/tip/ec80fde746e3ccf93895d25ae1a7071c9af52585 > > > Author: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> > > > AuthorDate: Thu, 26 May 2011 09:53:51 -0300 > > > Committer: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> > > > CommitDate: Thu, 26 May 2011 11:15:25 -0300 > > > > > > perf symbols: Handle /proc/sys/kernel/kptr_restrict > > > > Ok, things are much better now with kptr_restrict turned on - but i > > still see a few rough edges in practice. > > > > For example 'perf top' says: > > > > aldebaran:~/linux> perf top > > [kernel.kallsyms] with build id 122214021a666675f6e5ff97d70a85ce7139c0e7 not found, continuing without symbols > > The (null) file can't be used > > > > Now we've confused the user, havent we? :-) > > The ones that do: > > # echo -1 > /proc/sys/kernel/perf_event_paranoid > > Right? Or the ones that do: aldebaran:~> ./loop_yield & [1] 7557 aldebaran:~> aldebaran:~> perf top -p 7557 [kernel.kallsyms] with build id 44d9a989eabbd79e486bc079d6b743d397c204e0 not found, continuing without symbols The (null) file can't be used Also, we might eventually make perf events more widely available by default, so even default 'perf top' might do something useful for unprivileged users. > Trying that, not usually something I do :) i run all my perf workflow unprivileged - as root you can always typo catastrophically :-) Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|