-
Notifications
You must be signed in to change notification settings - Fork 736
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
Update to use the new LoadStoreHandler API on Power #11305
Merged
fjeremic
merged 7 commits into
eclipse-openj9:master
from
aviansie-ben:power-loadstorehandler
Feb 17, 2021
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
e7c26c2
Disable prefetching for aloadi nodes on 64-bit
aviansie-ben a98159d
Add OMRLoadStoreHandler.cpp to builds
aviansie-ben 7322e41
Update write barriers to use the new LoadStoreHandler API
aviansie-ben 46fc477
Update read barriers to use the new LoadStoreHandler API
aviansie-ben bf696f2
Update simple read monitors to use the new LoadStoreHandler API
aviansie-ben b93e826
Update copyright dates to 2021
aviansie-ben f8d77f9
Remove assert at Julian's request
aviansie-ben File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This looks like conditions being misplaced originally. This current fix certainly is not in line with the intention of prefetch optimization. Prefetch surely is beneficial performance-wise to 64bit non-compressed.
The conditions should read something like: if (is-objectReference-load && hotness-testing && CPU-testing)
Applies to the next change too.
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.
While I agree that prefetching certainly could be applied in these circumstances, extending the prefetching optimization to handle this case correctly is out-of-scope for this PR. As the commit message clarifies, the previous implementation was not performing prefetching for such nodes either, but the way this was being achieved was slightly different. This change does not make prefetching not occur where it previously would, but simply makes
insertPrefetchIfNecessary
safe to call onaloadi
nodes under 64-bit, as it would otherwise segfault.Previously, we were simply failing to call
insertPrefetchIfNecessary
at all under the problematic conditions, thus sidestepping the problem. In commoning up code between the load evaluators intoLoadStoreHandler
, all of these evaluators need to behave uniformly and thus now callinsertPrefetchIfNecessary
unconditionally, with it being up to that method alone to make the decision as to whether to perform prefetching. This also avoids leaking implementation details of OpenJ9's prefetching into OMR.If you'd like, I can open an issue for extending this support in the future, though.
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.
certainly need a follow-up item
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.
Opened #11803