Skip to content

Conversation

wks
Copy link
Contributor

@wks wks commented Sep 18, 2021

Added a VMOp_ThirdPartyHeapOperation for the third-party heap to perform
stop-the-world GC.

SafepointSynchronize::begin() no longer report "thread has stopped".

@wks wks force-pushed the fix-safepoint-sync2 branch from 3cde79c to a395aa6 Compare September 22, 2021 13:05
@wks wks marked this pull request as ready for review September 22, 2021 13:07
Added a VMOp_ThirdPartyHeapOperation for the third-party heap to perform
stop-the-world GC.

SafepointSynchronize::begin() no longer report "thread has stopped" to
the third-party heap.  Instead the third-party heap should scan stacks
during stop-the-world.
@wks wks force-pushed the fix-safepoint-sync2 branch from a395aa6 to fae99f8 Compare September 24, 2021 05:25
@qinsoon qinsoon merged commit 6dc618e into mmtk:jdk-11.0.11+6-mmtk Sep 28, 2021
k-sareen pushed a commit that referenced this pull request Apr 13, 2022
Added a VMOp_ThirdPartyHeapOperation for the third-party heap to perform
stop-the-world GC.

SafepointSynchronize::begin() no longer report "thread has stopped" to
the third-party heap.  Instead the third-party heap should scan stacks
during stop-the-world.
k-sareen pushed a commit that referenced this pull request Feb 14, 2023
Added a VMOp_ThirdPartyHeapOperation for the third-party heap to perform
stop-the-world GC.

SafepointSynchronize::begin() no longer report "thread has stopped" to
the third-party heap.  Instead the third-party heap should scan stacks
during stop-the-world.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants