[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110513204530.GF8950@ghostprotocols.net>
Date: Fri, 13 May 2011 17:45:30 -0300
From: Arnaldo Carvalho de Melo <acme@...hat.com>
To: Wim Heirman <wim@...rman.net>
Cc: Ingo Molnar <mingo@...e.hu>, David Ahern <dsahern@...il.com>,
linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
Frédéric Weisbecker <fweisbec@...il.com>,
Brice Goglin <Brice.Goglin@...ia.fr>
Subject: Re: perf-stat per thread results
Em Fri, May 13, 2011 at 10:32:58PM +0200, Wim Heirman escreveu:
> > It's supposed to do that if --stat is specified, and it used to work - see this
> > commit:
> > 8d51327090ac: perf report: Fix and improve the displaying of per-thread event counters
> > and the output there:
> >
> > # PID TID cache-misses cache-references
> > 4658 4659 495581 3238779
> > 4658 4662 498246 3236823
> > 4658 4663 499531 3243162
> > which appears to be roughly what Wim is asking for, AFAICT.
> Thanks, this is exactly what I'm looking for. In 2.6.32 (Ubuntu 10.04)
> it works, although if I use --pid rather than the -- <command> variant
> the first thread seams to be missing. In 2.6.38 (Ubuntu 11.04) the
> first thread is missing in both use cases, and I get one column per
> processor (which in itself is fine).
Can you try after applying the patches in this message:
http://marc.info/?l=linux-kernel&m=130385067430510&w=2
and report your results?
If it fixes the problems you're experiencing, please provide a:
Tested-by: Wim Heirman <wim@...rman.net>
So that I can add when sending them to Ingo.
Thanks,
- Arnaldo
--
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