From: Yunlong Song <yunlong.song@huawei.com>
To: <dzickus@redhat.com>
Cc: <dsahern@gmail.com>, <fweisbec@gmail.com>, <jmario@redhat.com>,
<efault@gmx.de>, <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>, <rfowles@redhat.com>,
<eranian@google.com>,
"acme@kernel.org >> Arnaldo Carvalho de Melo" <acme@kernel.org>,
<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>,
<fowles@inreach.com>, Namhyung Kim <namhyung@kernel.org>,
<andi@firstfloor.org>
Subject: [Questions] perf c2c: What's the current status of perf c2c?
Date: Wed, 9 Dec 2015 12:06:44 +0800 [thread overview]
Message-ID: <5667A8D4.4090601@huawei.com> (raw)
Hi, Don,
I am interested in the perf c2c tool, which is introduced in: http://lwn.net/Articles/588866/
However, I found that this tool has not been applied to the mainline tree of perf, Why? It was first
introduced in Feb. 2014. What's its current status now? Does it have a new version or a repository
somewhere else? And does it support Haswell?
--
Thanks,
Yunlong Song
next reply other threads:[~2015-12-09 4:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 4:06 Yunlong Song [this message]
2015-12-09 8:04 ` [Questions] perf c2c: What's the current status of perf c2c? 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
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=5667A8D4.4090601@huawei.com \
--to=yunlong.song@huawei.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=dzickus@redhat.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fowles@inreach.com \
--cc=fweisbec@gmail.com \
--cc=jmario@redhat.com \
--cc=jolsa@kernel.org \
--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 \
/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.