From: David Ahern <dsahern@gmail.com>
To: Jovi Zhang <bookjovi@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf: fix perf-lock report coredump
Date: Tue, 10 Jul 2012 20:20:12 -0600 [thread overview]
Message-ID: <4FFCE2DC.1090201@gmail.com> (raw)
In-Reply-To: <CACV3sbK7jUCDZxGBs3RUYnQ4s+VyEt7VYeRKD50F07zZrYKgCg@mail.gmail.com>
On 7/10/12 7:06 PM, Jovi Zhang wrote:
> From 4b363bf16c12b76788fbace1475123b7214ae58d Mon Sep 17 00:00:00 2001
> From: Jovi Zhang <bookjovi@gmail.com>
> Date: Wed, 11 Jul 2012 16:53:57 +0800
> Subject: [PATCH] perf: fix perf-lock report coredump
>
> Check sample type event raw_data is existed in perf.data firstly,
> then invoke process_raw_event, otherwise it will coredump.
Does this fix it for you:
http://lkml.org/lkml/2012/7/6/405
Also does 'perf lock record' work for you? If so can you send me your
kernel config file?
Thanks,
David
next prev parent reply other threads:[~2012-07-11 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 1:06 [PATCH] perf: fix perf-lock report coredump Jovi Zhang
2012-07-11 2:20 ` David Ahern [this message]
2012-07-11 5:14 ` Jovi Zhang
2012-07-12 3:49 ` 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=4FFCE2DC.1090201@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=acme@infradead.org \
--cc=bookjovi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.