-
Notifications
You must be signed in to change notification settings - Fork 734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update z/TPF code cache strategy #17555
Conversation
@0xdaryl pls help find a reviewer for this. |
If it makes it easier, all the updates are within z/TPF guard macros and have been running for 2 years. |
@0xdaryl Much appreciated. |
Jenkins test sanity xlinux jdk17 Changes are guarded with ifdefs that OpenJ9 testing does not enable so light sanity testing seems sufficient. |
@mpirvu : this PR introduces changes to the zTPF code cache allocation that are all guarded behind zTPF ifdefs. In spite of that, do you have any comments you want to make prior to merging? |
676be9a
to
be9f349
Compare
@mpirvu : if you approve, I'll launch some light testing on this. |
be9f349
to
08f0fe0
Compare
08f0fe0
to
25dde4c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Jenkins test sanity zlinux jdk17 |
Pull request represents z/TPF OS platform specific updates to code cache strategy.
z/TPF has a second 64-bit heap region managed by the mmap function which allows Java processes to work better with traditional non-java applications. The update enables processes to detect whether the feature is enabled and to allocate the JIT code cache from it based on a heuristic meaningful only to z/TPF. The fallback is to use the other pre-existing 64-bit heap reagion limited by a MAXXMMES system heap configuration unique to the z/TPF platform.