All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@google.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
	"Jiri Olsa" <jolsa@redhat.com>,
	"Yunlong Song" <yunlong.song@huawei.com>,
	"Don Zickus" <dzickus@redhat.com>,
	"David Ahern" <dsahern@gmail.com>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Joe Mario" <jmario@redhat.com>, "Mike Galbraith" <efault@gmx.de>,
	"Paul Mackerras" <paulus@samba.org>,
	"Richard Fowles" <rfowles@redhat.com>,
	"acme@kernel.org >> Arnaldo Carvalho de Melo" <acme@kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Jiri Olsa" <jolsa@kernel.org>,
	"wangnan0@huawei.com >> Wang Nan" <wangnan0@huawei.com>,
	"Richard Fowles" <fowles@inreach.com>,
	"Namhyung Kim" <namhyung@kernel.org>
Subject: Re: [Questions] perf c2c: What's the current status of perf c2c?
Date: Wed, 9 Dec 2015 09:15:04 -0800	[thread overview]
Message-ID: <CABPqkBSR+haJr-uzn3xjbP5aZ_x70FDi7ufgJi3wW7PitfqBwA@mail.gmail.com> (raw)
In-Reply-To: <20151209165807.GP15533@two.firstfloor.org>

Hi,

On Wed, Dec 9, 2015 at 8:58 AM, Andi Kleen <andi@firstfloor.org> wrote:
>> > 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.
>
If I recall the c2c tool is giving you more than the bouncing line. It shows you
the offset inside the line and the participating CPUs.

  reply	other threads:[~2015-12-09 17:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  4:06 [Questions] perf c2c: What's the current status of perf c2c? Yunlong Song
2015-12-09  8:04 ` Jiri Olsa
2015-12-09  8:12   ` Wangnan (F)
2015-12-09  9:11     ` Jiri Olsa
2015-12-09  9:34   ` Peter Zijlstra
2015-12-09 10:58     ` Peter Zijlstra
2015-12-09 11:09     ` Joe Mario
     [not found]     ` <1891297138.17374838.1449658964938.JavaMail.zimbra@redhat.com>
2015-12-09 14:03       ` Peter Zijlstra
2015-12-09 16:58     ` Andi Kleen
2015-12-09 17:15       ` Stephane Eranian [this message]
2015-12-09 17:21         ` Andi Kleen
2015-12-09 19:48           ` Stephane Eranian
2015-12-09 20:41         ` Joe Mario
2015-12-10  2:36           ` Yunlong Song

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=CABPqkBSR+haJr-uzn3xjbP5aZ_x70FDi7ufgJi3wW7PitfqBwA@mail.gmail.com \
    --to=eranian@google.com \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=dsahern@gmail.com \
    --cc=dzickus@redhat.com \
    --cc=efault@gmx.de \
    --cc=fowles@inreach.com \
    --cc=fweisbec@gmail.com \
    --cc=jmario@redhat.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=rfowles@redhat.com \
    --cc=wangnan0@huawei.com \
    --cc=yunlong.song@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.