From: Jiri Olsa <jolsa@redhat.com>
To: He Kuang <hekuang@huawei.com>
Cc: bigeasy@linutronix.de, jolsa@kernel.org, acme@kernel.org,
a.p.zijlstra@chello.nl, mingo@redhat.com, wangnan0@huawei.com,
linux-kernel@vger.kernel.org,
Alexandre Montplaisir <alexmonthy@voxpopuli.im>
Subject: Re: [PATCH 1/2] perf data: Show error message when ctf setup failed
Date: Thu, 9 Apr 2015 11:46:54 +0200 [thread overview]
Message-ID: <20150409094654.GA1321@krava.brq.redhat.com> (raw)
In-Reply-To: <55263608.2070301@huawei.com>
On Thu, Apr 09, 2015 at 04:19:20PM +0800, He Kuang wrote:
> Hi, jirka
> On 2015/4/9 1:45, Jiri Olsa wrote:
> >On Wed, Apr 08, 2015 at 12:49:19PM +0800, He Kuang wrote:
> >>Show message when errors occurred during ctf conversion setup.
> >>
> >>Before this patch:
> >> $ ./perf data convert --to-ctf=ctf
> >> $ echo $?
> >> 255
> >>
> >>After this patch:
> >> $ ./perf data convert --to-ctf=ctf
> >> Error during CTF convert setup.
> >so I have like 5 more patches from the original CTF set
> >which I'm holding until all works with tracecompass:
> > http://marc.info/?l=linux-kernel&m=142736197610573&w=2
> >
> >Is it working for you? How do you test resulted CTF data?
> >
> >anyway the patch looks ok, just small nit below
>
> I tested by using babeltrace binary and it works.
>
> After receiving your reply, I test on the latest tracecompass. A
> folder named 'ctf' is showed instead of the expected file
> 'ctf-data', this folder only contains the raw metadata and
> perf-stream files but not analysed.
CC-ing Alexandre from tracecompass devel ^^^
jirka
next prev parent reply other threads:[~2015-04-09 9:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 4:49 [PATCH 1/2] perf data: Show error message when ctf setup failed He Kuang
2015-04-08 4:49 ` [PATCH 2/2] perf data: Fix ctf_writer setupenv failure He Kuang
2015-04-08 17:59 ` Jiri Olsa
2015-04-09 7:38 ` He Kuang
2015-04-09 19:57 ` Jérémie Galarneau
2015-04-10 7:39 ` He Kuang
2015-04-10 12:38 ` Jiri Olsa
2015-04-08 17:45 ` [PATCH 1/2] perf data: Show error message when ctf setup failed Jiri Olsa
2015-04-09 7:56 ` [PATCHv2 1/2] perf data: Show error message when conversion failed He Kuang
2015-04-09 9:45 ` Jiri Olsa
2015-04-18 14:00 ` Jiri Olsa
2015-04-09 8:19 ` [PATCH 1/2] perf data: Show error message when ctf setup failed He Kuang
2015-04-09 9:46 ` Jiri Olsa [this message]
2015-04-09 14:37 ` Alexandre Montplaisir
2015-04-10 12:05 ` Jiri Olsa
2015-04-10 12:37 ` Jiri Olsa
2015-04-13 20:30 ` Jérémie Galarneau
2015-04-14 17:47 ` Jérémie Galarneau
2015-04-18 13:58 ` Jiri Olsa
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=20150409094654.GA1321@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=alexmonthy@voxpopuli.im \
--cc=bigeasy@linutronix.de \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=wangnan0@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).