Skip to content

8358748: Large page size initialization fails with assert "page_size must be a power of 2" #25994

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

Closed
wants to merge 5 commits into from

Conversation

nelanbu
Copy link
Contributor

@nelanbu nelanbu commented Jun 26, 2025

The VM now exits gracefully if -XX:LargePageSizeInBytes is set to a non power of two value, instead of asserting. After this change, SizeTTest.java failed because the tested values are not valid for -XX:LargePageSizeInBytes (LargePageSizeInBytesConstraintFunc returns JVMFlag::VIOLATES_CONSTRAINT). Therefore, I updated the test to use NUMASpaceResizeRate, since I believe that it only requires a flag of type size_t.

Before the change:

java -XX:+UseLargePages -XX:LargePageSizeInBytes=6 -version

# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (workspace/open/src/hotspot/share/runtime/os.cpp:2449), pid=1885945, tid=1885946
# assert(is_power_of_2(page_size)) failed: page_size must be a power of 2: 0x6

After the change:

java -XX:+UseLargePages -XX:LargePageSizeInBytes=6 -version

LargePageSizeInBytes ( 6 ) must be a power of 2
Improperly specified VM option 'LargePageSizeInBytes=6'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8358748: Large page size initialization fails with assert "page_size must be a power of 2" (Bug - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25994/head:pull/25994
$ git checkout pull/25994

Update a local copy of the PR:
$ git checkout pull/25994
$ git pull https://git.openjdk.org/jdk.git pull/25994/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25994

View PR using the GUI difftool:
$ git pr show -t 25994

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25994.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jun 26, 2025

👋 Welcome back nelanbu! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jun 26, 2025

@nelanbu This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8358748: Large page size initialization fails with assert "page_size must be a power of 2"

Reviewed-by: ayang, dholmes

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 16 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@albertnetymk, @dholmes-ora) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added the rfr Pull request is ready for review label Jun 26, 2025
@openjdk
Copy link

openjdk bot commented Jun 26, 2025

@nelanbu The following label will be automatically applied to this pull request:

  • hotspot-runtime

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@mlbridge
Copy link

mlbridge bot commented Jun 26, 2025

Webrevs

@dholmes-ora
Copy link
Member

The -XX:LargePageSizeInBytes flag seems poorly specified. You can't use an arbitrary value in bytes as a large page size - that is just non-sensical. But I'm not sure this should be a hard error rather than applying "ergonomics" and rounding the supplied value to the nearest power-of-2 (with a warning this has happened).

@bridgekeeper
Copy link

bridgekeeper bot commented Jul 28, 2025

@nelanbu This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@openjdk
Copy link

openjdk bot commented Aug 6, 2025

@nelanbu this pull request can not be integrated into master due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:

git checkout JDK-8358748
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push

@openjdk openjdk bot added the merge-conflict Pull request has merge conflict with target branch label Aug 6, 2025
@openjdk openjdk bot removed the merge-conflict Pull request has merge conflict with target branch label Aug 19, 2025
@albertnetymk
Copy link
Member

Therefore, I updated the test to use NUMASpaceResizeRate, since I believe that it only requires a flag of type size_t.

How about LargePageHeapSizeThreshold? It's size_t also. (NUMASpaceResizeRate is a ParallelGC-only flag.)

@nelanbu
Copy link
Contributor Author

nelanbu commented Aug 19, 2025

Therefore, I updated the test to use NUMASpaceResizeRate, since I believe that it only requires a flag of type size_t.

How about LargePageHeapSizeThreshold? It's size_t also. (NUMASpaceResizeRate is a ParallelGC-only flag.)

LargePageHeapSizeThreshold would be better. I'll replace it. Thanks for the suggestion @albertnetymk!

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Aug 19, 2025
Copy link
Member

@dholmes-ora dholmes-ora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine. Thnaks

@nelanbu
Copy link
Contributor Author

nelanbu commented Aug 20, 2025

Thanks a lot for the reviews! Can I also get a sponsor?

@nelanbu
Copy link
Contributor Author

nelanbu commented Aug 20, 2025

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Aug 20, 2025
@openjdk
Copy link

openjdk bot commented Aug 20, 2025

@nelanbu
Your change (at version 6dfa4a2) is now ready to be sponsored by a Committer.

@albertnetymk
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Aug 20, 2025

Going to push as commit 40bc083.
Since your change was applied there have been 16 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Aug 20, 2025
@openjdk openjdk bot closed this Aug 20, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Aug 20, 2025
@openjdk
Copy link

openjdk bot commented Aug 20, 2025

@albertnetymk @nelanbu Pushed as commit 40bc083.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot-runtime [email protected] integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

4 participants