Date: Thu, 10 Dec 2009 08:23:51 +0100
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
Message-ID: <20091210072351.GF16874@elte.hu>
References: <1260391208-6808-1-git-send-regression-fweisbec@gmail.com>
 <4B206A18.2030607@cn.fujitsu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B206A18.2030607@cn.fujitsu.com>
User-Agent: Mutt/1.5.20 (2009-08-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 984
Lines: 25


* 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/