From: Ingo Molnar <mingo@elte.hu>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] perf sched: Add max delay time snapshot
Date: Thu, 10 Dec 2009 08:23:51 +0100 [thread overview]
Message-ID: <20091210072351.GF16874@elte.hu> (raw)
In-Reply-To: <4B206A18.2030607@cn.fujitsu.com>
* Xiao Guangrong <xiaoguangrong@cn.fujitsu.com> wrote:
> Frederic Weisbecker wrote:
>
> > When we have a maximum latency reported for a task, we need a
> > convenient way to find the matching location to the raw traces or to
> > perf sched map that shows where the task has been eventually
> > scheduled in. This gives a pointer to retrieve the events that
> > occured during this max latency.
>
> Then, we can cooperate with ftrace's data to know what the cpu is
> doing at that time.
What do you mean by mixing it with ftrace data? These events ought to be
a full replacement for the sched and wakeup tracers. In the long run we
want a single stream of events and phase out most of the pretty-printing
ftrace plugins.
Ingo
next prev parent reply other threads:[~2009-12-10 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 20:40 [PATCH] perf sched: Add max delay time snapshot Frederic Weisbecker
2009-12-10 3:25 ` Xiao Guangrong
2009-12-10 7:23 ` Ingo Molnar [this message]
2009-12-10 8:15 ` Xiao Guangrong
2009-12-10 8:27 ` Ingo Molnar
2009-12-10 8:46 ` Xiao Guangrong
2009-12-10 7:50 ` [tip:perf/urgent] " tip-bot for Frederic Weisbecker
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=20091210072351.GF16874@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=xiaoguangrong@cn.fujitsu.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