From: David Ahern <dsahern@gmail.com>
To: Stephane Eranian <eranian@google.com>, Don Zickus <dzickus@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
William Cohen <wcohen@redhat.com>
Subject: Re: mapping instructions to dynamic languages like java, python, ruby
Date: Tue, 22 Apr 2014 13:19:13 -0600 [thread overview]
Message-ID: <5356C0B1.8050709@gmail.com> (raw)
In-Reply-To: <CABPqkBTJ4==4FF2KLVGzvpGSX_RhHVZWUH5h9Vvi+XG_xJSUEQ@mail.gmail.com>
On 4/22/14, 1:05 PM, Stephane Eranian wrote:
> I intend to contribute that code for perf once it is finalized.
> Note that it uses a module developed by Sonny Rao to
> export the perf timestamp time source via a posix-clock.
> This clock discussion has been going on for a while and
> never reached a conclusion. So I decided to go with the
> simple posix-clock module for the time being.
I don't recall Sonny creating one. If you are referring to the one I
mention here:
https://github.com/dsahern/linux/blob/perf-full-monty/README.ahern
It's from Pawel Moll.
David
next prev parent reply other threads:[~2014-04-22 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 18:03 mapping instructions to dynamic languages like java, python, ruby Don Zickus
2014-04-22 18:26 ` Peter Zijlstra
2014-04-22 19:05 ` Stephane Eranian
2014-04-22 19:19 ` David Ahern [this message]
2014-04-22 21:23 ` Don Zickus
2014-04-23 6:03 ` Namhyung Kim
2014-04-22 20:54 ` Andi Kleen
2014-04-22 21:24 ` 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=5356C0B1.8050709@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wcohen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox