8269870: PS: Membar in PSPromotionManager::copy_unmarked_to_survivor_space could be relaxed#19764
8269870: PS: Membar in PSPromotionManager::copy_unmarked_to_survivor_space could be relaxed#19764albertnetymk wants to merge 2 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back ayang! A progress list of the required criteria for merging this PR into |
|
@albertnetymk 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: 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 75 new commits pushed to the
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 |
|
/contributor add mli |
|
@albertnetymk |
|
@albertnetymk The following label will be automatically applied to this pull request:
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. |
|
Thanks for working on this. :) I suppose with the removal of |
c1b5336 to
fb4a255
Compare
|
@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
|
Missed the |
| // Now we have to CAS in the header. | ||
| // Make copy visible to threads reading the forwardee. | ||
| oop forwardee = o->forward_to_atomic(new_obj, test_mark, memory_order_release); | ||
| oop forwardee = o->forward_to_atomic(new_obj, test_mark, memory_order_relaxed); |
There was a problem hiding this comment.
I think this needs a comment similar to what's in G1ParScanThreadState::do_copy_to_suvivor_space, e.g.
jdk/src/hotspot/share/gc/g1/g1ParScanThreadState.cpp
Lines 504 to 507 in f101e15
tschatzl
left a comment
There was a problem hiding this comment.
Lgtm.
Fwiw, now that it is established that nobody is looking at the object's contents, PR#17227 can be resurrected too.
|
Thanks for review. /integrate |
|
Going to push as commit b88af94.
Your commit was automatically rebased without conflicts. |
|
@albertnetymk Pushed as commit b88af94. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The acquire-release mem-barrier was probably used/required before but not any more. Inspiration taken from
G1ParScanThreadState::do_oop_evac.Progress
Issue
Reviewers
Contributors
<mli@openjdk.org>Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19764/head:pull/19764$ git checkout pull/19764Update a local copy of the PR:
$ git checkout pull/19764$ git pull https://git.openjdk.org/jdk.git pull/19764/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 19764View PR using the GUI difftool:
$ git pr show -t 19764Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19764.diff
Webrev
Link to Webrev Comment