8368989: Use NMethodMarkingScope and ThreadsClaimTokenScope in shenandoahSTWMark

[fandreuz]

Replace StrongRootsScope with ThreadsClaimTokenScope in shenandoahSTWMark to be more precise with what is needed and why.

• ShenandoahSTWMark uses MarkingNMethodClosure, so we also need NMethodMarkingScope.
• nworkers is guaranteed to be > 0

Passes tier1 and tier2 (fastdebug).

---

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-8368989: Use NMethodMarkingScope and ThreadsClaimTokenScope in shenandoahSTWMark (Enhancement - P4)

Reviewers

• Aleksey Shipilev (@shipilev - Reviewer)
• Albert Mingkun Yang (@albertnetymk - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27589

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back fandreuzzi! 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]

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

8368989: Use NMethodMarkingScope and ThreadsClaimTokenScope in shenandoahSTWMark

Reviewed-by: shade, ayang

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 8 new commits pushed to the master branch:

• 84e5d63: 8368885: NMT CommandLine tests can check for error better
• f49849a: 8368893: RISC-V: crash after JDK-8352673 on fastdebug version
• 6c2d383: 8368953: Document the reason why Serial/Parallel/G1 use zero as dirty card value
• ... and 5 more: https://git.openjdk.org/jdk/compare/9b02896b4725ef932a23be11ff76ce04bda0d652...master

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 (@shipilev, @albertnetymk) 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]

@fandreuz The following labels will be automatically applied to this pull request:

• hotspot-gc
• shenandoah

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

[mlbridge]

Webrevs

• 00: Full (442bc5be)