From: David Ahern <dsahern@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: "Xu, Anhua" <anhua.xu@intel.com>,
"acme@redhat.com" <acme@redhat.com>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
"mingo@elte.hu" <mingo@elte.hu>,
"paulus@samba.org" <paulus@samba.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tools: Exit recording if events have non matching sample type
Date: Fri, 21 Oct 2011 08:29:53 -0600 [thread overview]
Message-ID: <4EA181E1.5090101@gmail.com> (raw)
In-Reply-To: <4EA17EAE.8040905@gmail.com>
On 10/21/2011 08:16 AM, David Ahern wrote:
>
>
> On 10/21/2011 02:10 AM, Jiri Olsa wrote:
>> On Fri, Oct 21, 2011 at 03:18:31PM +0800, Xu, Anhua wrote:
>>> I installed the latest kernel and found without such patch( not sure if other patches were added besides this one). That following command works fine.
>>> perf record -o perf.data -e ext3:ext3_request_inode -e LLC-loads -- date '+%F'
>> hi,
>> was there any ext3 event stored? The issue should be hit when
>> processing stored events.. either in the atexit code or during
>> report.
>>
>> Following command freezes for me on 3.1.0-rc10-tip+:
>> ./perf record -o perf.data -e ext4:ext4_request_inode -e LLC-loads -- date '+%F'
>>
>
> With -B and it doesn't for me. Without the -B argument the backtrace
> shows it stuck here:
While it doesn't hang with the -B, the data file is worthless --
non-matching sample type. :-)
David
next prev parent reply other threads:[~2011-10-21 14:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 16:01 [PATCH] perf tools: Exit recording if events have non matching sample type Jiri Olsa
2011-09-29 22:05 ` Arnaldo Carvalho de Melo
2011-09-29 22:55 ` David Ahern
2011-10-03 10:22 ` Jiri Olsa
2011-10-03 16:27 ` Arnaldo Carvalho de Melo
2011-10-03 19:15 ` Jiri Olsa
2011-10-17 12:50 ` Jiri Olsa
2011-10-21 7:18 ` Xu, Anhua
2011-10-21 8:10 ` Jiri Olsa
2011-10-21 14:16 ` David Ahern
2011-10-21 14:29 ` David Ahern [this message]
2011-10-21 14:43 ` Jiri Olsa
2011-10-21 14:42 ` Jiri Olsa
-- strict thread matches above, loose matches on Subject: below --
2011-09-29 23:06 Arnaldo Carvalho de Melo
2011-09-29 23:33 ` David Ahern
2011-09-30 0:40 ` Arnaldo Carvalho de Melo
2011-09-30 0:58 ` David Ahern
2011-09-30 2:21 ` Arnaldo Carvalho de Melo
2011-09-30 2:41 ` David Ahern
2011-09-30 7:39 ` Peter Zijlstra
2011-10-04 4:14 ` David Ahern
2011-10-04 10:00 ` Peter Zijlstra
2011-10-04 13:41 ` 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=4EA181E1.5090101@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=anhua.xu@intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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