[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151209165807.GP15533@two.firstfloor.org>
Date: Wed, 9 Dec 2015 17:58:08 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Jiri Olsa <jolsa@...hat.com>,
Yunlong Song <yunlong.song@...wei.com>, dzickus@...hat.com,
dsahern@...il.com, fweisbec@...il.com, jmario@...hat.com,
efault@....de, paulus@...ba.org, rfowles@...hat.com,
eranian@...gle.com,
"acme@...nel.org >> Arnaldo Carvalho de Melo" <acme@...nel.org>,
mingo@...hat.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jiri Olsa <jolsa@...nel.org>,
"wangnan0@...wei.com >> Wang Nan" <wangnan0@...wei.com>,
fowles@...each.com, Namhyung Kim <namhyung@...nel.org>,
andi@...stfloor.org
Subject: Re: [Questions] perf c2c: What's the current status of perf c2c?
> > the plan for me is to to use it some more to prove it's useful
> > and kick it to be merged with perf at some point
>
> So I never really liked the c2c tool because it was so narrowly
> focussed, it only works on NUMA thingies IIRC.
It should work on all systems with an Intel Core (not Atom)
However it was never clear to me if the tool was any better
than simply sampling for
mem_load_uops_l3_hit_retired.xsnp_hitm:pp (local socket)
mem_load_uops_l3_miss_retired.remote_hitm:pp (remote socket)
which gives you instructions that reference bouncing cache lines.
-Andi
--
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