Loom Pinning: Manage J9VMThread->callOutCount - #15496
Conversation
e7f4551 to
fba9759
Compare
|
I'd prefer that the counter be managed in the places that need it, rather than testing the frame type in the common helper. I can think of two places that will need this - JNI callout and the call to JNI_OnLoad in the loadLibrary INL. Also, anywhere that calls back in to java to do a resolve (MH, ConstantValue, etc) should be considered a callout for now. |
fba9759 to
4c57cfc
Compare
Feedback addressed. Also, accounted for call-ins. |
4c57cfc to
72af9eb
Compare
In order to support if a Continuation is pinned, callOutCount is - incremented when a frame of a below type is build. - decremented when a frame of a below type is removed. Frame types, which have been accounted: - J9SF_FRAME_TYPE_JNI_NATIVE_METHOD - J9SF_FRAME_TYPE_NATIVE_METHOD - Call-in frame TODOs for the JIT (eclipse-openj9#15175): - Increment callOutCount in JNILinkage::buildJNICallOutFrame. - Decrement callOutCount in JNILinkage::restoreJNICallOutFrame. - Related frame type: J9SF_FRAME_TYPE_JIT_JNI_CALLOUT. Related: eclipse-openj9#15174 Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
72af9eb to
34f82f1
Compare
|
jenkins compile win jdk8 |
|
jenkins test sanity zlinux jdknext |
|
Lots of (likely unrelated) test failures. |
|
|
jenkins test sanity zlinux jdk19 |
In order to support if a
Continuationis pinned,callOutCountisFrame types, which have been accounted:
J9SF_FRAME_TYPE_JNI_NATIVE_METHODJ9SF_FRAME_TYPE_NATIVE_METHODTODOs for the JIT (#15175):
callOutCountinJNILinkage::buildJNICallOutFrame.callOutCountinJNILinkage::restoreJNICallOutFrame.J9SF_FRAME_TYPE_JIT_JNI_CALLOUT.Related: #15174
Signed-off-by: Babneet Singh sbabneet@ca.ibm.com