[GR-60208] [GR-52447] Trace FFM API calls in native image agent. #11270
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oracle-contributor-agreement
bot
added
the
OCA Verified
graalvmbot
force-pushed
the
fa/GR-60208/ffm_api_agent_support
branch
from
06a27f2 to
7cd3d39
Compare
graalvmbot
force-pushed
the
fa/GR-60208/ffm_api_agent_support
branch
from
7cd3d39 to
309e6d0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements agent support for FFM API usage.
The agent intercepts calls to
AbstractLinker.downcallHandle0andAbstractLinker.upcallStuband generates an appropriate foreign configuration file (i.e.foreign-config.json).It also attempts to crack the target method handle for upcalls in order to generate a direct upcall.
The descriptor string for memory layouts are generated by recursively traversing the parameter and return layouts. This should be the most reliable approach because the classes are public JDK classes and won't easily change. The downside is that this may involve quite some JNI calls.
An alternative would be to parse the string representation of a memory layout which uses an undocumented format (with the risk to be changed) and is also ambiguous in some cases.
This PR also adds support for foreign configurations to the
native-image-configuretool.