[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090126150002.GB9128@elte.hu>
Date: Mon, 26 Jan 2009 16:00:02 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Kevin Shanahan <kmshanah@...b.org.au>, Avi Kivity <avi@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Mike Galbraith <efault@....de>,
Frédéric Weisbecker <fweisbec@...il.com>,
bugme-daemon@...zilla.kernel.org
Subject: Re: [Bug #12465] KVM guests stalling on 2.6.28 (bisected)
* Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> Is there a way to add a wall-time column to this output so that we can
> see where the time goes?
yes, on tip/master:
http://people.redhat.com/mingo/tip.git/README
do something like this:
echo funcgraph-abstime > /debug/tracing/trace_options
when the function-graph plugin is active. This will activate the absolute
timestamps column in the trace output.
> Another something nice would be to have ctx switches like:
>
> foo-1 => bar-2 ran: ${time foo spend on the cpu} since: ${time bar spend away from the cpu}
>
> I'll poke me a little at this function graph tracer thingy to see if I
> can do that.
indeed, tracking the 'scheduling atom duration' would be very nice.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists