Thanks Gregory, I did mean CompiledMethodLoad. Thanks for the explanation about the state of JVMTI support in DRLVM and the caveat about -agentlib defaulting to interpreted mode for some simple JVMTI support. Adding -Dvm.use_interpreter=false did enabled the JIT for me [and the corresponding events]... Starting up eclipse this way, I see 4695 class loads and 16691 method JIT events. 364 of them are for secondary jits [jitting the same method multiple times].
I'll need to look at this a bit more closely. Some of the CompiledMethodLoad data for secondary jit events look a bit strange. It sounds like support is still early so this type of issue will likely be resolved as the VM and JIT evolve? For example, for org.eclipse.osgi.framework.internal.core.KeyedHashSet.getByKey(Ljava/lan g/Object;)Lorg/eclipse/osgi/framework/internal/core/KeyedElement; I see three CompiledMethodLoad events. VA Length Time 0x0000000000D196C0 0x000000000000039A 05/12-15:25:21 0x000000000B2D6D10 0x000000000000021C 05/12-15:25:41 0x0000000000D196C0 0x000000000000039A 05/12-15:25:41 It looks like the method is jitted once then 20 seconds later it is rejitted to a new address [and made smaller] then is immediately rejitted back to its original location and size. Thanks, Chris Elford Intel Middleware Products Division -----Original Message----- From: Gregory Shimansky [mailto:[EMAIL PROTECTED] Sent: Friday, May 12, 2006 3:08 PM To: [email protected] Subject: Re: [DRLVM] -- JVMTI support? On Friday 12 May 2006 22:18 Elford, Chris L wrote: > Hi all, > > I was working with the version of DRLVM that I compiled off of > JIRA-438. I tried it with a JVMTI agent using -agentlib:... It looks > like this version gives Class Load events. According to JVMTI, loading > eclipse loads 4,189 classes. > > I'm not seeing any Method Load Events though. Has anyone else tried > JIRA-438 with JVMTI and seen more events? If you mean CompiledMethodLoad event, you may not see it since when JVMTI is enabled on command line (-agentlib, -agentpath or -xrun options are specified) then by defaul VM currently enables interpreter mode. It is made because JVMTI is not implemented to any usable extent in VM in JIT mode yet. But in interpreter mode it is already usable for simple debugging. So if you want to see CompiledMethodLoad event you need to explicitly specify -Dvm.use_interpreter=false on the VM command line. This will allow you to receive some JIT/interpreter independent events like ClassLoad or ClassPrepare and several profiling related events like CompiledMethodLoad or DynamicCodeGenerated. If that doesn't work, let me know. It should :) -- Gregory Shimansky, Intel Middleware Products Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
