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: Wed, 11 Jul 2012 21:49:46 -0600 [thread overview]
Message-ID: <4FFE495A.9070101@gmail.com> (raw)
In-Reply-To: <CACV3sbLMOVm=WFofjc8-3pRvy1JduYVKWGY=EakjfhtftZPQ9A@mail.gmail.com>
On 7/10/12 11:14 PM, Jovi Zhang wrote:
>> Does this fix it for you:
>> http://lkml.org/lkml/2012/7/6/405
>>
> Yeah, same problem.
> But the question is if there have some sample event with raw data in
> perf.data, are we still just exit(1)?
> or let perf-lock only report those sample events with raw data?
perf-lock uses 4 tracepoints. tracepoints add -R (raw data) to events.
So, if the perf.data does not have tracepoints, there is no need for
perf-lock info or report subcommands to proceed.
David
prev parent reply other threads:[~2012-07-12 3:49 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
2012-07-11 5:14 ` Jovi Zhang
2012-07-12 3:49 ` David Ahern [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=4FFE495A.9070101@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox