[GR-70643] Virtualize native memory in Espresso #12692
Merged
+4,111
−1,159
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
added 3 commits
December 10, 2025 11:05
An abstract NativeMemory class was added and linked as a field to NativeAccess. Moreover the newly added EspressoOption.nativeMemory enables selecting native memory implementations. Currently this is only available with the no-native backend since there needs to be strong synergy between Java and Native reads and writes to native memory. Implemenations of NativeMemory include: - Unsafe NativeMemory (it accesses the host memory and forwards it to the guest) - ByteArray NativeMemory (Memory gets divided into chunks and every chunk holds an addressable byte-array) - MemorySegmemt NativeMemory (Memory gets divided into chunks and every chunk holds an addressable MemorySegmemt)
Basically just makes EspressoLibs use the newly added NativeMemory interface. Meaning all function that involved off-heap accesses were rewritten. Additionally the functionaily to read and write from certain address in TruffleIO was added.
Ensures that all memory operations in Espresso flow through the NativeMemory layer. This mainly involves adapting Unsafe substitutions and the NativeUtils class. For the latter, we needed to ensure that all callers pass a NativeMemory instance to the called static methods. In most cases, this was straightforward as the caller had access to the context, but for the structs, it required some rewriting of the StructProcessor class.
oracle-contributor-agreement
bot
added
the
OCA Verified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Virtualize native memory in Espresso
Adjustments were made such that all guest memory accesses now are going through this NativeMemory class.
Implemenations of NativeMemory include:
- Unsafe NativeMemory (it accesses the host memory and forwards it to the guest)
- ByteArray NativeMemory (Memory gets divided into chunks and every chunk holds an addressable byte-array)
- MemorySegmemt NativeMemory (Memory gets divided into chunks and every chunk holds an addressable MemorySegment)