From: Andi Kleen <andi@firstfloor.org>
To: Kenth Eriksson <kenth.eriksson@transmode.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: perf fails to mmap data file (JFFS2)
Date: Thu, 03 Sep 2015 11:57:32 -0700 [thread overview]
Message-ID: <87d1xz49gj.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1441266585059.29731@transmode.com> (Kenth Eriksson's message of "Thu, 3 Sep 2015 07:49:45 +0000")
Kenth Eriksson <kenth.eriksson@transmode.com> writes:
> perf on 4.1 fails to mmap the perf data file (in
> __perf_session__process_events) with error code 22 (invalid
> argument). I believe the JFFS2 file system does not support PROT_READ
> and MAP_SHARED. How can this be fixed? Can we change from MAP_SHARED
> to MAP_PRIVATE, or is there a reason to make it shared?
MAP_PRIVATE should be fine.
-Andi
next prev parent reply other threads:[~2015-09-03 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 7:49 perf fails to mmap data file (JFFS2) Kenth Eriksson
2015-09-03 18:57 ` Andi Kleen [this message]
2015-09-04 7:00 ` [PATCH] Fix mmap error for perf data file. Not all file systems, e.g. JFFS2, support MAP_SHARED Kenth Eriksson
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=87d1xz49gj.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=kenth.eriksson@transmode.com \
--cc=linux-kernel@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