-
Notifications
You must be signed in to change notification settings - Fork 7.9k
JIT: Add IBT support #8636
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
Merged
Merged
JIT: Add IBT support #8636
Changes from all commits
Commits
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 hidden or 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 hidden or 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
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.
Can we enable/disable generation of
endbr
ar run-time? e.g. thorough new bit inopcache.jit
directive?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'm not sure if this is really necessary...
Can you share some CET vs non-CET benchmarks results? (at least Zend/bench.php)
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.
My concern is that runtime enable/disable may cause inconsistency, i.e., jitted code has
endbr
and gcced code doesn't. Our current method mimics or aligns with the behavior of gcc who enable/disable generation ofendbr
at compile time.GCC:
When compiled with
gcc -fcf-protection=full
(default) orgcc -fcf-protection=branch
, the MACRO__CET__
is defined andendbr
is inserted. It will also emit a property namedIBT
to ELF header.Execution flow:
Once ld.so see
IBT
property in ELF header, it issues an arch_prctl() syscall to kernel to enable HW/CPU CET engine.Benchmarks results:
I will run and share Google PKB benchmark result next week. Below are quick Zend/bench.php results:
BTW, when HW/CPU CET engine is OFF, the
endbr
is regarded asnop
. For this case, even the app hasendbr
inside, the perf impact is negligible.