From: Jiri Olsa <jolsa@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
Mike Galbraith <efault@gmx.de>,
Stephane Eranian <eranian@google.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH 0/2] perf record: mmap output file - v3
Date: Thu, 7 Nov 2013 11:06:19 +0100 [thread overview]
Message-ID: <20131107100619.GB1251@krava.brq.redhat.com> (raw)
In-Reply-To: <527A81B8.7040505@gmail.com>
On Wed, Nov 06, 2013 at 10:51:52AM -0700, David Ahern wrote:
> On 11/4/13, 11:31 AM, Jiri Olsa wrote:
> >hi,
> >after discussion with David, sending his change
> >updated into the new data file object.
> >
> >David's original post:
> > http://marc.info/?l=linux-kernel&m=138180575328977&w=2
> >
> >Here's the change:
> > git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> > perf/mmap1
> >
>
> Not having any luck with these patches. Basic use case:
>
> perf trace record -a -- sleep 5
> perf trace --summary
>
> With your patches I get a parse error. With my latest versions
> everything works clean.
hum,
perf trace --summary seems stuck in a loop, but that's no
different from current acme's perf/core.
Anyway I'll postpone the change till your v3 goes in
and go from there.
jirka
next prev parent reply other threads:[~2013-11-07 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 18:31 Jiri Olsa
2013-11-04 18:31 ` [PATCH 1/2] perf tools: Add perf_data__write implementation into perf_data_file object Jiri Olsa
2013-11-04 18:31 ` [PATCH 2/2] perf tools: Add perf_data_file__write mmap support Jiri Olsa
2013-11-06 17:51 ` [PATCH 0/2] perf record: mmap output file - v3 David Ahern
2013-11-07 10:06 ` Jiri Olsa [this message]
2013-11-07 14:32 ` 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=20131107100619.GB1251@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®