From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <dsahern@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf record: mmap fails when specifying process/thread
Date: Wed, 16 Feb 2011 21:53:31 -0200 [thread overview]
Message-ID: <20110216235331.GC26039@ghostprotocols.net> (raw)
In-Reply-To: <4D5BF0B1.7080602@gmail.com>
Em Wed, Feb 16, 2011 at 08:43:45AM -0700, David Ahern escreveu:
> Latest perf-core (pulled 5 minutes ago):
>
> # ps -C sshd
> PID TTY TIME CMD
> 961 ? 00:00:00 sshd
> 1042 ? 00:00:00 sshd
>
> # /tmp/build-perf/perf record -v -fo/tmp/perf.data -p 1042
> Warning: ... trying to fall back to cpu-clock-ticks
>
> Fatal: failed to mmap with 22 (Invalid argument)
>
>
> It works fine with -a argument and when a command is given, but fails
> with the -p or -t argument.
In my radar, perf/urgent works tho, kinda made me lazy due to compound with
unrelated company work :-\ Need to fix that ASAP.
- Arnaldo
next prev parent reply other threads:[~2011-02-16 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 15:43 perf record: mmap fails when specifying process/thread David Ahern
2011-02-16 23:53 ` Arnaldo Carvalho de Melo [this message]
2011-02-17 0:01 ` David Ahern
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=20110216235331.GC26039@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--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).