From: David Ahern <dsahern@gmail.com>
To: "Carl E. Love" <cel@us.ibm.com>, Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, acme@redhat.com,
peterz@infradead.org, mingo@elte.hu, ak@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org,
sukadev@linux.vnet.ibm.com, sonnyrao@chromium.org,
johnmccutchan@google.com, adrian.hunter@intel.com,
pawel.moll@arm.com
Subject: Re: [PATCH v4 3/4] perf inject: add jitdump mmap injection support
Date: Wed, 25 Mar 2015 16:15:32 -0600 [thread overview]
Message-ID: <55133384.1030902@gmail.com> (raw)
In-Reply-To: <1427316113.5585.6.camel@oc3328482554>
On 3/25/15 2:41 PM, Carl E. Love wrote:
> I do not fine the directory tools/build in the linux kernel tree. I am
> wondering if the Build file and the tools/build directory might be part
> of your source tree build environment?
you want to use acme's perf/core branch from
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
next prev parent reply other threads:[~2015-03-25 22:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 22:25 [PATCH v4 0/4] perf: add support for profiling jitted code Stephane Eranian
2015-03-24 22:25 ` [PATCH v4 1/4] perf: Use monotonic clock as a source for timestamps Stephane Eranian
2015-03-24 22:25 ` [PATCH v4 2/4] perf tools: add Java demangling support Stephane Eranian
2015-03-25 20:34 ` Carl E. Love
2015-03-26 0:57 ` Stephane Eranian
2015-03-26 1:03 ` David Ahern
2015-03-25 22:18 ` Arnaldo Carvalho de Melo
2015-03-24 22:25 ` [PATCH v4 3/4] perf inject: add jitdump mmap injection support Stephane Eranian
2015-03-25 20:41 ` Carl E. Love
2015-03-25 22:15 ` David Ahern [this message]
2015-03-25 21:17 ` Carl E. Love
2015-03-26 8:00 ` Adrian Hunter
2015-03-24 22:25 ` [PATCH v4 4/4] perf tools: add JVMTI agent library Stephane Eranian
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=55133384.1030902@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=cel@us.ibm.com \
--cc=eranian@google.com \
--cc=johnmccutchan@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=pawel.moll@arm.com \
--cc=peterz@infradead.org \
--cc=sonnyrao@chromium.org \
--cc=sukadev@linux.vnet.ibm.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.