From: Andi Kleen <andi@firstfloor.org>
To: David Ahern <dsahern@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Andrew Vagin <avagin@openvz.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH 3/4] perf: teach perf inject to merge sched_stat_* and sched_switch events (v2)
Date: Tue, 28 Aug 2012 00:14:23 +0200 [thread overview]
Message-ID: <20120827221423.GE16230@one.firstfloor.org> (raw)
In-Reply-To: <503BED07.9030404@gmail.com>
On Mon, Aug 27, 2012 at 03:56:23PM -0600, David Ahern wrote:
> On 8/27/12 2:51 PM, Andi Kleen wrote:
> >Andrew Vagin <avagin@openvz.org> writes:
> >>
> >>My code saves sched_switch event for each process and when it meets
> >>stat_iowait, it reports the sched_switch event, because this event
> >>contains a correct callchain. By another words it replaces all
> >>stat_iowait events on proper sched_switch events.
> >
> >Is there any way to generalize this to arbitary events? I found myself
> >writing scripts to compute lengths between various events. But I
>
> You mean delta-time between events? I have toyed around with patches to
> perf-script for this -- dt between same event on a cpu, dt between
> consecutive events on a cpu, dt between events for a thread, etc.
I did the same. But I then realized perf script is the wrong approach.
perf script is a deadend as far as perf is concerned.
You want a filter that generates another perf.data that you then can
view in the browser. So perf inject is the better model.
-Andi
next prev parent reply other threads:[~2012-08-27 22:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 12:56 [PATCH 0/4] perf: Teach perf tool to profile sleep times (v2) Andrew Vagin
2012-08-07 12:56 ` [PATCH 1/4] perf: teach "perf inject" to work with files (v2) Andrew Vagin
2012-10-26 15:09 ` [tip:perf/core] perf inject: Work with files tip-bot for Andrew Vagin
2012-08-07 12:56 ` [PATCH 2/4] perf: synthesize_sample gets evsel instead of session Andrew Vagin
2012-08-07 12:56 ` [PATCH 3/4] perf: teach perf inject to merge sched_stat_* and sched_switch events (v2) Andrew Vagin
2012-08-25 11:47 ` Frederic Weisbecker
2012-08-27 7:22 ` Andrey Wagin
2012-08-27 20:51 ` Andi Kleen
2012-08-27 21:56 ` David Ahern
2012-08-27 22:14 ` Andi Kleen [this message]
2012-08-29 8:27 ` Andrew Vagin
2012-10-26 15:10 ` [tip:perf/core] perf inject: Merge sched_stat_* and sched_switch events tip-bot for Andrew Vagin
2012-08-07 12:56 ` [PATCH 4/4] perf: mark a dso if it's used Andrew Vagin
2012-10-26 15:11 ` [tip:perf/core] perf inject: Mark " tip-bot for Andrew Vagin
2012-08-08 0:32 ` [PATCH 0/4] perf: Teach perf tool to profile sleep times (v2) Namhyung Kim
2012-08-08 5:02 ` Andrey Wagin
2012-08-08 5:30 ` Namhyung Kim
2012-08-08 7:24 ` Andrey Wagin
2012-08-09 0:37 ` Namhyung Kim
2012-08-09 12:56 ` Andrey Wagin
2012-08-24 13:32 ` Andrey Wagin
2012-08-24 17:59 ` 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=20120827221423.GE16230@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=avagin@openvz.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).