Skip to content

Conversation

Hamlin-Li
Copy link

@Hamlin-Li Hamlin-Li commented Sep 9, 2025

Hi,
Can you help to review this patch?

Dependent extensions could be improved in several ways.

Currently, the dependent cpu extensions are processed in 2 separate places:

  1. update_flag() when calling VM_Version::setup_cpu_available_features()
  2. at the end of VM_Version::common_initialize().

And, dependency relationship can only be expressed in (1:1) way, can not be expressed (1:N) way, but in fact some extensions can depend on several different other extensions, for example, zvfh depends on zvf and rvv. It's would be better to support this (1:N) relationship.

So, this PR brings several benefits:

  1. VM options directly related to CPU extensions are automatically set, and they are all set in one place.
  2. keep synchronization between CPU extensions (information in RVFeatureValue) and and VM options. Previously, code in common_initialize wont' sync to RVFeatureValue, unless do it manually, which is error-prone.
  3. support to express (1:N) dependency relationship among cpu extensions and related vm options.

Thanks!

Test

$TEST_JDK/bin/java -XX:+UnlockExperimentalVMOptions -XX:-UseRVV -XX:+PrintFlagsFinal -version | grep -e UseRVV -e UseZvbc -e UseZvfh -e UseZvkn
OpenJDK 64-Bit Server VM warning: Cannot enable UseZvbb on cpu without any of the supports: v (disabled)
OpenJDK 64-Bit Server VM warning: Cannot enable UseZvbc on cpu without any of the supports: v (disabled)
OpenJDK 64-Bit Server VM warning: Cannot enable UseZvfh on cpu without any of the supports: v (disabled), Zfh (enabled)
     bool UseRVV                                   = false                             {ARCH diagnostic} {command line}
     bool UseZvbc                                  = false                           {ARCH experimental} {default}
     bool UseZvfh                                  = false                             {ARCH diagnostic} {default}
     bool UseZvkn                                  = false                           {ARCH experimental} {default}
$TEST_JDK/bin/java -XX:+UnlockExperimentalVMOptions -XX:-UseZfh -XX:+PrintFlagsFinal -version | grep -e UseRVV -e UseZvbc -e UseZvfh -e UseZvkn
OpenJDK 64-Bit Server VM warning: Cannot enable UseZvfh on cpu without any of the supports: v (enabled), Zfh (disabled)
     bool UseRVV                                   = true                              {ARCH diagnostic} {default}
     bool UseZvbc                                  = true                            {ARCH experimental} {default}
     bool UseZvfh                                  = false                             {ARCH diagnostic} {default}
     bool UseZvkn                                  = false                           {ARCH experimental} {default}

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-8367253: RISC-V: refactor dependent cpu extensions (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27171

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 9, 2025

👋 Welcome back mli! 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 Sep 9, 2025

@Hamlin-Li 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:

8367253: RISC-V: refactor dependent cpu extensions

Reviewed-by: fyang, luhenry

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 42 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.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk
Copy link

openjdk bot commented Sep 9, 2025

@Hamlin-Li The following label will be automatically applied to this pull request:

  • hotspot

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.

@openjdk openjdk bot added hotspot [email protected] rfr Pull request is ready for review labels Sep 9, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 9, 2025

Webrevs

@openjdk
Copy link

openjdk bot commented Sep 12, 2025

⚠️ @Hamlin-Li This pull request contains merges that bring in commits not present in the target repository. Since this is not a "merge style" pull request, these changes will be squashed when this pull request in integrated. If this is your intention, then please ignore this message. If you want to preserve the commit structure, you must change the title of this pull request to Merge <project>:<branch> where <project> is the name of another project in the OpenJDK organization (for example Merge jdk:master).

@openjdk
Copy link

openjdk bot commented Sep 25, 2025

@Hamlin-Li 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 refactor-dependent-cpu-extensions
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 Sep 25, 2025
@openjdk openjdk bot removed the merge-conflict Pull request has merge conflict with target branch label Sep 25, 2025
Copy link
Member

@RealFYang RealFYang left a comment

Choose a reason for hiding this comment

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

Hi, Thanks for the refactoring work. I have a small question.

Copy link
Member

@RealFYang RealFYang left a comment

Choose a reason for hiding this comment

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

Latest version LGTM.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Sep 29, 2025
@Hamlin-Li
Copy link
Author

Latest version LGTM.

Thank you!

@Hamlin-Li
Copy link
Author

/integrate

@openjdk
Copy link

openjdk bot commented Sep 29, 2025

Going to push as commit 9d71af1.
Since your change was applied there have been 44 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 Sep 29, 2025
@openjdk openjdk bot closed this Sep 29, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Sep 29, 2025
@openjdk
Copy link

openjdk bot commented Sep 29, 2025

@Hamlin-Li Pushed as commit 9d71af1.

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

@Hamlin-Li Hamlin-Li deleted the refactor-dependent-cpu-extensions branch September 29, 2025 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot [email protected] integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants