From: John Levon <levon@movementarian.org>
To: "Villacis, Juan" <juan.villacis@intel.com>
Cc: Andi Kleen <ak@muc.de>, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.x] additional kernel event notifications
Date: Tue, 23 Sep 2003 11:16:32 +0100 [thread overview]
Message-ID: <20030923101632.GA85283@compsoc.man.ac.uk> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D372001732DEC9E@scsmsx402.sc.intel.com>
On Mon, Sep 22, 2003 at 06:16:14PM -0700, Villacis, Juan wrote:
> There are several languages and tools besides Java which can jit code.
> Perl6 (using interpreters like Parrot) and Python (using interpreters
> like Psycho) are examples of this and it is not yet clear what
> interfaces they will provide to allow for JVMPI like functionality. We
First, "we might need it" is not generally considered a good enough
rationale for extra code by the kernel people.
Second, if there is no help from a runtime for tracking JITted code
memory -> source lines, I do not see how your hooks could possibly help.
Either way you need help from the VM of the target program (be it
Parrot, Python or whatever).
> would still like to be able to provide something useful to the users of
What would "something useful" be in particular ?
> From what we can see in the Oprofile driver code, if there is no dcookie
> for a corresponding EIP, the EIP information is discarded and the
Correct.
But we're talking about making oprofile useful for your purposes - that
can and will involve changes. In particular it's trivial to add an
option to oprofile to output the raw EIP is no dentry could be matched.
> As long as there exists a userspace API similar to the JVMPI for a
> particular DGC generator, and as long as the profiling tool is using
> that API, then yes, it seems like this method would work. But this
> isn't the case we are worried about.
I hate to be a pain, but I'm still missing a concrete explanation of an
*actual* case you are worried about. It's rather difficult to discuss
this stuff in the abstract.
regards
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is over.
next prev parent reply other threads:[~2003-09-23 10:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 1:16 [PATCH 2.6.x] additional kernel event notifications Villacis, Juan
2003-09-23 10:16 ` John Levon [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-22 6:23 Villacis, Juan
2003-09-22 5:59 Villacis, Juan
2003-09-22 11:07 ` John Levon
[not found] <xAZi.1DR.1@gated-at.bofh.it>
2003-09-20 2:02 ` Andi Kleen
2003-09-20 0:57 Villacis, Juan
2003-09-20 2:23 ` John Levon
2003-09-19 21:18 Villacis, Juan
2003-09-19 21:28 ` Andrew Morton
2003-09-20 17:24 ` Anton Blanchard
2003-09-19 20:00 Nakajima, Jun
2003-09-19 19:32 Villacis, Juan
2003-09-19 19:35 ` Andrew Morton
2003-09-18 6:20 Villacis, Juan
2003-09-19 18:18 ` Jesse Barnes
2003-09-19 18:28 ` Andrew Morton
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=20030923101632.GA85283@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=juan.villacis@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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