Skip to content

Conversation

@zhengyu123
Copy link
Contributor

@zhengyu123 zhengyu123 commented May 27, 2022

Please review the patch that fixes Loom support in Shenandoah GC.

  • stackChunkOop is a special oop that contains stack metadata, we need to utilize nmethod entry barrier to mark, evacuate and update stack metadata.
  • During evacuation and reference updating phase, we can not guarantee all metadata in stackChunkOop is deeply good, so I force it to take slow path for the correctness, will try to optimize it later in separate CR.
  • Shenandoah uses similar way to arm and disarm nmethod as the new mechanism introduced in JDK-8284161. We may want to migrate to it in followup CR.

Test:

  • tier1 with ShenandoahGC (Linux x86_64 and Windows x64)
  • tier2 with Shenandoah GC (Linux x86_64 and Windows x64)
  • hotspot_gc_shenandoah on Linux x86_32
  • tier1 with ShenandoahGC + Loom (Linux x86_64 and Windows x64)
  • tier2 with ShenandoahGC + Loom (Linux x86_64 and Windows x64)

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

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8924/head:pull/8924
$ git checkout pull/8924

Update a local copy of the PR:
$ git checkout pull/8924
$ git pull https://git.openjdk.java.net/jdk pull/8924/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 8924

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8924.diff

@bridgekeeper
Copy link

bridgekeeper bot commented May 27, 2022

👋 Welcome back zgu! 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 May 27, 2022

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

  • hotspot
  • 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.

@openjdk openjdk bot added hotspot hotspot-dev@openjdk.org shenandoah shenandoah-dev@openjdk.org labels May 27, 2022
@zhengyu123 zhengyu123 marked this pull request as ready for review May 27, 2022 23:16
@openjdk openjdk bot added the rfr Pull request is ready for review label May 27, 2022
@mlbridge
Copy link

mlbridge bot commented May 27, 2022

Webrevs


heap->set_concurrent_mark_in_progress(true);

_mark.start_mark();
Copy link
Member

Choose a reason for hiding this comment

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

Style: call start_mark() here maybe? Matches the use of end_mark() elsewhere.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okay. I am award of asymmetry, but not sure this is better.

Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

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

I am okay with most of it, but still concerned with the injecting new code into hot marking loops.

Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

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

I still have a question: now that closures drop do_metadata, does that mean we always traverse metadata now? Which means we can remove half of the closures? For example, ShenandoahMarkUpdateRefsClosure and ShenandoahMarkUpdateRefsMetadataClosure are pretty much the same, right? We can leave ShenandoahMarkUpdateRefsClosure only then?

@zhengyu123
Copy link
Contributor Author

ShenandoahMarkUpdateRefsMetadataClosure

Yes, we always walk metadata now.

And right, I need to look into duplicated closures. But can we do that in separate CR? Another round of tests going to take a couple of days, and I want to get this in before RDP1.

Thanks.

Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

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

All right then!

@openjdk
Copy link

openjdk bot commented Jun 1, 2022

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

8286829: Shenandoah: fix Shenandoah Loom support

Reviewed-by: shade

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

  • 67ecd30: 8287398: Allow concurrent execution of hotspot docker tests
  • 8071b23: 8287237: (fs) Files.probeContentType returns null if filename contains hash mark on Linux
  • 774928f: 8287625: ProblemList jdk/jshell/HighlightUITest.java on all platforms
  • e3791ec: 8287491: compiler/jvmci/errors/TestInvalidDebugInfo.java fails new assert: assert((uint)t < T_CONFLICT + 1) failed: invalid type #
  • f8eb7a8: 8287512: continuationEntry.hpp has incomplete definitions
  • b2b4ee2: 8287233: Crash in Continuation.enterSpecial: stop: tried to execute native method as non-native
  • 168b226: 8282662: Use List.of() factory method to reduce memory consumption
  • 48f19e4: 8287453: RenderPerfTest incorrectly measures performance
  • 0ef3d85: 8287552: riscv: Fix comment typo in li64
  • e0e15de: 8287366: Improve test failure reporting in GHA
  • ... and 89 more: https://git.openjdk.java.net/jdk/compare/6cc4bb1169f34bc091cad3e2deec37cd5585e8d5...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.

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

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jun 1, 2022
@zhengyu123
Copy link
Contributor Author

Thanks, @shipilev

@zhengyu123
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Jun 1, 2022

Going to push as commit 239ac2a.
Since your change was applied there have been 99 commits pushed to the master branch:

  • 67ecd30: 8287398: Allow concurrent execution of hotspot docker tests
  • 8071b23: 8287237: (fs) Files.probeContentType returns null if filename contains hash mark on Linux
  • 774928f: 8287625: ProblemList jdk/jshell/HighlightUITest.java on all platforms
  • e3791ec: 8287491: compiler/jvmci/errors/TestInvalidDebugInfo.java fails new assert: assert((uint)t < T_CONFLICT + 1) failed: invalid type #
  • f8eb7a8: 8287512: continuationEntry.hpp has incomplete definitions
  • b2b4ee2: 8287233: Crash in Continuation.enterSpecial: stop: tried to execute native method as non-native
  • 168b226: 8282662: Use List.of() factory method to reduce memory consumption
  • 48f19e4: 8287453: RenderPerfTest incorrectly measures performance
  • 0ef3d85: 8287552: riscv: Fix comment typo in li64
  • e0e15de: 8287366: Improve test failure reporting in GHA
  • ... and 89 more: https://git.openjdk.java.net/jdk/compare/6cc4bb1169f34bc091cad3e2deec37cd5585e8d5...master

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jun 1, 2022
@openjdk openjdk bot closed this Jun 1, 2022
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jun 1, 2022
@openjdk
Copy link

openjdk bot commented Jun 1, 2022

@zhengyu123 Pushed as commit 239ac2a.

💡 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 hotspot-dev@openjdk.org integrated Pull request has been integrated shenandoah shenandoah-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

3 participants