From: Jiri Olsa <jolsa@redhat.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [BUG] perf timechart segfault
Date: Wed, 2 Oct 2013 13:59:36 +0200 [thread overview]
Message-ID: <20131002115935.GD10099@krava.brq.redhat.com> (raw)
In-Reply-To: <CALkWK0mCbnBZXJNFyX3odoGb1pvGs7ox1mOiFacqX98ewBOGKw@mail.gmail.com>
On Wed, Oct 02, 2013 at 05:03:48PM +0530, Ramkumar Ramachandra wrote:
> Hi Jiri,
>
> Jiri Olsa wrote:
> > what perf version are you running?
>
> I'm running off the one in torvalds/linux.git.
>
> $ perf --version
> perf version 3.12.rc3.g34b22d5
>
> The log of builtin-timechart.c shows that it was last touched by you
> three months ago: 5936678 (perf timechart: Remove event types
> framework only user, 2013-07-11). Are there some patches awaiting
> merge that I'm missing?
looks like you're missing this one:
(git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux perf/core)
perf tools: Add default handler for mmap2 events
commit e0e3e2d9a522b2230d395922fde9c6ea928ae7f8
Author: David Ahern <dsahern@gmail.com>
Date: Sun Sep 22 19:44:59 2013 -0600
Not sure if this one plus some other MMAP2 David's fixies
are on its way up, but if not I guess Arnaldo's planning
to push them out eventually ;-)
jirka
next prev parent reply other threads:[~2013-10-02 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 11:06 [BUG] perf timechart segfault Ramkumar Ramachandra
2013-10-02 11:19 ` Jiri Olsa
2013-10-02 11:33 ` Ramkumar Ramachandra
2013-10-02 11:59 ` Jiri Olsa [this message]
2013-10-02 12:13 ` Ingo Molnar
2013-10-02 15:33 ` Arnaldo Carvalho de Melo
2013-10-02 13:10 ` Ramkumar Ramachandra
2013-10-02 13:26 ` Ingo Molnar
2013-10-02 16:12 ` Arnaldo Carvalho de Melo
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=20131002115935.GD10099@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=artagnon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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