mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: adrian.hunter@intel.com, acme@redhat.com, a.p.zijlstra@chello.nl,
	linux-kernel@vger.kernel.org
Subject: Re: [perf tool] record failure with 3.14-rc4
Date: Mon, 24 Feb 2014 18:36:40 +0100	[thread overview]
Message-ID: <20140224173639.GA7597@krava.brq.redhat.com> (raw)
In-Reply-To: <20140224172440.GF2553@mudshark.cambridge.arm.com>

On Mon, Feb 24, 2014 at 05:24:41PM +0000, Will Deacon wrote:
> Hi guys,
> 
> If I try to run perf record as a non-root user, I end up with the following
> (unhelpful) error:
> 
>   $ perf record -e cycles ls
>   [...]
>   Not enough memory for reading perf file header
> 
> This is because the addresses in /proc/kallsyms always read as 0x0 when
> viewed by a non-privileged user, causing kallsyms__get_function_start to
> return 0x0 in args.start. machine__create_kernel_maps then treats this as
> an error an returns -1 to perf_session__create_kernel_maps, causing
> perf_session__new to fail and perf to exit.
> 
> The perf tool code in 3.13 is perfectly happy creating maps at 0x0, but I
> can see this has changed quite substantially in the recent merge window.
> 
> Any ideas? We could fix kallsyms__get_function_start to return < 0 on
> failure then fix the checks in the callers. Adrian?
hi,
not sure it's related, but i sent out rfc some time ago
for similar bad error messages:
  http://marc.info/?l=linux-kernel&m=138572558210216&w=2

maybe it could be updated for your case as well,
I'll try to check deeply later

jirka

      reply	other threads:[~2014-02-24 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 17:24 Will Deacon
2014-02-24 17:36 ` Jiri Olsa [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=20140224173639.GA7597@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will.deacon@arm.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

all inboxes | Powered by JetHome®