-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8304138: [JVMCI] Test FailedSpeculation existence before appending. #13022
Conversation
👋 Welcome back yzheng! A progress list of the required criteria for merging this PR into |
@mur47x111 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. |
/label remove hotspot |
/label add hotspot-compiler |
@mur47x111 |
@mur47x111 |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that it is better than before.
But without some kind of lock several threads can add the same speculation data in the window between new check and adding data to the list.
@@ -846,7 +855,7 @@ bool FailedSpeculation::add_failed_speculation(nmethod* nm, FailedSpeculation** | |||
guarantee(is_aligned(fs, sizeof(FailedSpeculation*)), "FailedSpeculation objects must be pointer aligned"); | |||
guarantee_failed_speculations_alive(nm, failed_speculations_address); | |||
|
|||
FailedSpeculation** cursor = failed_speculations_address; | |||
cursor = failed_speculations_address; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not continue from cursor
value from previous check loop?
Can the list be modified by other threads in between?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It cannot be modified in between. Addressed in e8c7eec by continuing from cursor
Right. We can bear a few redundant FailedSpeculation entries, and would like to avoid locking in this fast path. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good.
Please, re-test with latest changes.
@mur47x111 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 60 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. 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 (@vnkozlov, @dougxc) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Yes, it would do what you are saying but I don't like infinite loops like that with conditional exists.
|
@vnkozlov your suggestion eagerly allocates a new |
Okay. You are the "boss" for this code ;^) |
/integrate |
@mur47x111 |
/sponsor |
Going to push as commit 7503ecc.
Your commit was automatically rebased without conflicts. |
@dougxc @mur47x111 Pushed as commit 7503ecc. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Upon uncommon_trap, JVMCI runtime appends a FailedSpeculation entry to the nmethod using an atomic operation. It becomes a performance bottleneck when there is a large amount of (virtual) threads deoptimizing in the nmethod. In this PR, we test if a FailedSpeculation exists in the list before appending it.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/13022/head:pull/13022
$ git checkout pull/13022
Update a local copy of the PR:
$ git checkout pull/13022
$ git pull https://git.openjdk.org/jdk pull/13022/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 13022
View PR using the GUI difftool:
$ git pr show -t 13022
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13022.diff