Messages in this thread |  | | | Date | Tue, 23 Sep 2003 11:16:32 +0100 | | From | John Levon <> | | Subject | Re: [PATCH 2.6.x] additional kernel event notifications |
| |
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |