Don't map systemcfg on Power in checkpoint mode #7351
Draft
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.
On Power
omrtime_current_time_millis
andomrtime_hires_clock
can use the timebase register to very quickly get the current time. This requires mmapping the special/proc/ppc64/systemcfg
file.Some security modules (e.g. SELinux) prevent systemcfg from being mapped by user processes. If we take a checkpoint in an environment that that allows systemcfg to be mapped it will not be restorable in an environment that forbids it.
This patch disables the mapping of systemcfg in checkpoint mode, which will force the omrtime functions to fall back to conventional Linux time APIs.