optee_ta: close persistent object once synced #4
Conversation
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
Changes NVMem.c _plat_WriteBack() operation to open/close the TEE objects related to the 512byte block only when there are accessed in storage. NVMem initialization function now closes the TEE object handles once read or created with initialization data. This change is useful on devices where OP-TEE run with a small secure memory (few hundreds of kByte). OP-TEE core, at least up to release tag 4.4.0, consumes about 500 bytes per opened object by a TA. Keeping the 32 objects of fTPM TA always open puts a high 20kB pressure on OP-TEE core heap for these devices. Signed-off-by: Etienne Carriere <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes NVMem.c _plat_WriteBack() operation to open/close the TEE objects related to the 512byte block only when there are accessed in storage. NVMem initialization function now closes the TEE object handles once read or created with initialization data.
This change is useful on devices where OP-TEE run with a small secure memory (few hundreds of kByte). OP-TEE core, at least up to release tag 4.4.0, consumes about 500 bytes per opened object by a TA. Keeping the 32 objects of fTPM TA always open puts a high 20kB pressure on OP-TEE core heap for these devices.