From: Jiri Olsa <jolsa@redhat.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [BUG] Junk output from perf test
Date: Mon, 7 Oct 2013 09:21:24 +0200 [thread overview]
Message-ID: <20131007072124.GA1013@krava.brq.redhat.com> (raw)
In-Reply-To: <CALkWK0=JXd5KJ1NAEiKJtTm3EKGqBVPLB=3hqYwfGsp6SRrLyA@mail.gmail.com>
On Mon, Oct 07, 2013 at 11:47:13AM +0530, Ramkumar Ramachandra wrote:
> Hi,
>
> `perf test` doesn't give me a clean run; it seems to be out-of-date. I
> spent many hours on tracing "parse events tests" with gdb, but
> preprocessor macros and other complexity make my job very difficult. I
> haven't determined where the warnings in #5 are coming from exactly,
> but it seems to be the codepath starting from test__all_tracepoints().
> Before I spend more hours debugging this, I want to make sure that I'm
> not wasting my time; can you reproduce this?
heya,
yep.. some of them are known to be broken, for some you'd
need the very last kernel to work properly, let's see..
>
> Thanks.
>
> -- 8< --
> $ perf test
> 1: vmlinux symtab matches kallsyms : FAILED!
> 2: detect open syscall event : Ok
> 3: detect open syscall event on all cpus : Ok
> 4: read samples using the mmap interface : Ok
> 5: parse events tests : Warning:
> bad op token {
> Warning: bad op token {
> Warning: bad op token {
> Warning: bad op token {
> Warning: function is_writable_pte not defined
> Warning: function jiffies_to_msecs not defined
> Warning: function jiffies_to_msecs not defined
> Warning: function scsi_trace_parse_cdb not defined
> Warning: function scsi_trace_parse_cdb not defined
> Warning: function scsi_trace_parse_cdb not defined
> Warning: function scsi_trace_parse_cdb not defined
> Warning: unknown op '{'
> Warning: unknown op '{'
> Warning: function xen_hypercall_name not defined
> Warning: function xen_hypercall_name not defined
> Warning: function sizeof not defined
> Warning: function sizeof not defined
> Warning: function sizeof not defined
> Warning: function sizeof not defined
> Warning: function sizeof not defined
> Warning: function sizeof not defined
> Warning: function sizeof not defined
> Warning: function sizeof not defined
> Warning: function sizeof not defined
> Ok
this one is libtracevent issue, and is fixed by adding
plugins support posted in here:
http://marc.info/?l=linux-kernel&m=137803257921043&w=2
I need to update and repost it..
> 6: x86 rdpmc test : Ok
> 7: Validate PERF_RECORD_* events & perf_sample fields : Ok
> 8: Test perf pmu format parsing : Ok
> 9: Test dso data interface : Ok
> 10: roundtrip evsel->name check : Ok
> 11: Check parsing of sched tracepoints fields : Ok
> 12: Generate and check syscalls:sys_enter_open event fields: Ok
> 13: struct perf_event_attr setup : Ok
> 14: Test matching and linking multiple hists : Ok
> 15: Try 'use perf' in python, checking link problems : Ok
> 16: Test breakpoint overflow signal handler : Ok
> 17: Test breakpoint overflow sampling : Ok
> 18: Test number of exit event of a simple workload : Ok
> 19: Test software clock events have valid period values : Ok
> 20: Test converting perf time to TSC : (not supported) Ok
> 21: Test object code reading :[btrfs]
> with build id 97dc0c1d4aab8c3aba31c776c8c6137ccce5428a not found,
> continuing without symbols
> FAILED!
not sure why those failed.. Adrian?
> 22: Test sample parsing : Ok
> 23: Test using a dummy software event to keep tracking : (not supported) Ok
I think you need latest kernel for this one
thanks,
jirka
next prev parent reply other threads:[~2013-10-07 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 6:17 [BUG] Junk output from perf test Ramkumar Ramachandra
2013-10-07 7:21 ` Jiri Olsa [this message]
2013-10-07 7:34 ` Adrian Hunter
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=20131007072124.GA1013@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--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