From: Milian Wolff <milian.wolff@kdab.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf trace: Problems initializing symbol libraries!
Date: Mon, 23 May 2016 12:05:13 +0200 [thread overview]
Message-ID: <3135861.RyWs4xx6Gt@milian-kdab2> (raw)
In-Reply-To: <20160517150617.GA28790@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Tuesday, May 17, 2016 12:06:17 PM CEST Arnaldo Carvalho de Melo wrote:
> Em Tue, May 17, 2016 at 09:51:44AM +0200, Milian Wolff escreveu:
> > On Monday, May 16, 2016 5:13:59 PM CEST Arnaldo Carvalho de Melo wrote:
> > > So, the problem is not with what is in my perf/core branch, its that
> > > ubuntu
> > > 16.04's kernel comes with kptr_restrict defaulting to 1, I have to get
> > > that
> > > warning emitted by 'perf record' into 'perf trace'.
> >
> > that makes it work for me. I'll include the line to set kptr_restrict to 0
> > into my "perf init" script that elevates the restrictions.
>
> That will not be strictly needed with what I have now on my perf/core
> branch, where it will just warn the user if/when symbol resolution is
> needed and kptr_restrict=1.
>
> Thanks for the report, tested on fedora 23 with kptr_restrict set to 1
> and then again on ubuntu 16.04, default kernel sysctl values.
Much appreciated, thanks a lot Arnaldo!
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
prev parent reply other threads:[~2016-05-23 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 12:05 perf trace: Problems initializing symbol libraries! Milian Wolff
2016-05-12 18:10 ` Arnaldo Carvalho de Melo
2016-05-16 11:31 ` Milian Wolff
2016-05-16 13:15 ` Arnaldo Carvalho de Melo
2016-05-16 20:13 ` Arnaldo Carvalho de Melo
2016-05-17 7:51 ` Milian Wolff
2016-05-17 15:06 ` Arnaldo Carvalho de Melo
2016-05-23 10:05 ` Milian Wolff [this message]
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=3135861.RyWs4xx6Gt@milian-kdab2 \
--to=milian.wolff@kdab.com \
--cc=acme@kernel.org \
--cc=linux-perf-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).