From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, paulus@samba.org, hpa@zytor.com,
mingo@redhat.com, eranian@google.com, tzanussi@gmail.com,
penberg@cs.helsinki.fi, torvalds@linux-foundation.org,
efault@gmx.de, peterz@infradead.org, davej@redhat.com,
davem@davemloft.net, fweisbec@gmail.com, kees.cook@canonical.com,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/urgent] perf symbols: Handle /proc/sys/kernel/kptr_restrict
Date: Thu, 26 May 2011 18:28:05 -0300 [thread overview]
Message-ID: <20110526212805.GB30593@ghostprotocols.net> (raw)
In-Reply-To: <20110526193946.GA6363@elte.hu>
Em Thu, May 26, 2011 at 09:39:46PM +0200, Ingo Molnar escreveu:
> Secondly, even though i have the proper 'vmlinux' in cwd, i get half
> a page long warnings on perf record warning me about the vmlinux:
>
> WARNING: Kernel address maps (/proc/{kallsyms,modules}) are restricted, check /proc/sys/kernel/kptr_restrict.
>
> Samples in kernel functions may not be resolved if a suitable
> vmlinux file is not found in the buildid cache or in the vmlinux
> path.
>
> ...
>
> But a vmlinux file *is* in the cwd.
Well, there was no assumption that 'perf report' would run on the same
directory as 'perf record', the user may have moved to a different
directory or transferred the perf.data file to a different machine.
Also it would have to check that the vmlinux on the path is suitable
(that build-id matches), currently it does that just at 'perf report'
time, that is when it will need to use it. At record time we just
collect the build-ids.
With that in mind, how do you think it should be phrased?
- Arnaldo
next prev parent reply other threads:[~2011-05-26 21:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 19:21 [tip:perf/urgent] perf symbols: Handle /proc/sys/kernel/kptr_restrict tip-bot for Arnaldo Carvalho de Melo
2011-05-26 19:39 ` Ingo Molnar
2011-05-26 21:20 ` Arnaldo Carvalho de Melo
2011-05-27 8:38 ` Ingo Molnar
2011-05-26 21:28 ` Arnaldo Carvalho de Melo [this message]
2011-05-27 8:35 ` Ingo Molnar
2011-05-27 15:46 ` Linus Torvalds
2011-05-27 15:57 ` Arnaldo Carvalho de Melo
2011-05-26 21:30 ` Arnaldo Carvalho de Melo
2011-05-27 8:42 ` Ingo Molnar
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=20110526212805.GB30593@ghostprotocols.net \
--to=acme@redhat.com \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tzanussi@gmail.com \
/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