-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8331572: Allow using OopMapCache outside of STW GC phases #610
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
❗ This change is not yet ready to be integrated. |
This backport pull request has now been updated with issue from the original commit. |
21c0383
to
9883745
Compare
9883745
to
b2438fb
Compare
Webrevs
|
|
/issue add JDK-8334594 |
@shipilev |
WIP. Unclean backport to improve GC and general stack walk performance when walking interpreted frames.
The point of uncleanliness comes from the way we hook up the cleanup notifications to Service Thread. In later JDKs, JDK-8329488 made Service Thread wake up regularly to do various cleanups. In JDK 21, we still need to hook up the clean up to the "usual" place in safepoint epilog.
Additional testing:
all
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/610/head:pull/610
$ git checkout pull/610
Update a local copy of the PR:
$ git checkout pull/610
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/610/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 610
View PR using the GUI difftool:
$ git pr show -t 610
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/610.diff
Webrev
Link to Webrev Comment