[PAL/Linux-SGX] AEX-Notify 3/5: Add AEX-Notify enabling code #2034
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.
Description of the changes
Part 3 in AEX-Notify series.
This is a preparatory PR for AEX-Notify support. This PR:
sgx.experimental_enable_aex_notify
manifest option.See also related PRs and discussions:
How to test this PR?
CI is enough to test that old flows are not broken.
Testing new manifest option
sgx.experimental_enable_aex_notify
manually:sgx.experimental_enable_aex_notify = true
to HelloWorld CI examplePlatform with no AEX-Notify hardware feature
Platform with AEX-Notify hardware feature but old Linux
(Linux kernel received AEX-Notify support in v6.2. Below I'm testing with Linux v5.15.)
If you wonder why Linux v5.15 enclave init fails with EACCES, check these sources:
And compare with Linux v6.2:
Platform with AEX-Notify hardware feature and new Linux
No changes from the master branch, as AEX-Notify is detected and on-enclave-startup enabled, but not dynamically enabled for enclave threads (see the
#ifdef
in the code).This change is