RISC-V vthread support for JVM intrinsic monitors

[RealFYang]

This ported vthread support for JVM intrinsic monitors to linux-riscv64 platform.

Testing on linux-riscv64:

• make test TEST="hotspot_loom jdk_loom" (release & fastdebug)
• make test TEST=tier1/2/3 (release)
• make test TEST=hotspot:tier4 (release)

---

Progress

• Change must not contain extraneous whitespace

Reviewers

• Patricio Chilano Mateo (@pchilano - Committer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 212

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/loom/pull/212.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

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

[openjdk]

@RealFYang 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:

RISC-V vthread support for JVM intrinsic monitors

Reviewed-by: pchilanomate

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 no new commits pushed to the fibers branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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 (@pchilano) 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).

[mlbridge]

Webrevs

• 02: Full - Incremental (e0bb7ccf)
• 01: Full - Incremental (649a8b5a)
• 00: Full (663cad33)

[robehn]

Nice work!

[pchilano]

Great! I see test jdk/java/lang/Thread/virtual/Parking.java should also have os.arch=="riscv64" added.

[RealFYang]

Great! I see test jdk/java/lang/Thread/virtual/Parking.java should also have os.arch=="riscv64" added.

Thanks for finding this! Seems that I missed this test somehow. Added and tested with both release and fastdebug builds on linux-riscv64.

[AlanBateman]

Thanks for finding this! Seems that I missed this test somehow. Added and tested with both release and fastdebug builds on linux-riscv64.

Thanks for the update. Once all ports that support VMContinuations are aligned then I think we can drop this @requires and have them be selected with @requires vm.continuations like the other tests.

[pchilano]

Great, thanks @RealFYang!

[AlanBateman]

@RealFYang If you "/integrate" then we should be able to sponsor.

[RealFYang]

All right. Let's get this integrated. Thanks everyone for having a look.
/integrate

[openjdk]

@RealFYang
Your change (at version e0bb7cc) is now ready to be sponsored by a Committer.

[AlanBateman]

/sponsor

[openjdk]

Going to push as commit 5a3deae.

[openjdk]

@AlanBateman @RealFYang Pushed as commit 5a3deae.

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