You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
Currently, when creating Aes256GcmKeyBuffer inside function test_idekm_tdisp, using below command to run requester will result in a big stack consumption.
cargo run --release -p spdm-requester-emu --no-default-features --features=spdm-ring,hashed-transcript-data,test_stack_size,test_heap_size,is_sync
While as PR #191 does, moving the Aes256GcmKeyBuffer creation out of function test_idekm_tdisp, the stack consumption of function test_idekm_tdisp can be optimized a lot. Need to root cause this issue.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
REF: #186 , #191
Currently, when creating Aes256GcmKeyBuffer inside function test_idekm_tdisp, using below command to run requester will result in a big stack consumption.
While as PR #191 does, moving the Aes256GcmKeyBuffer creation out of function test_idekm_tdisp, the stack consumption of function test_idekm_tdisp can be optimized a lot. Need to root cause this issue.
The text was updated successfully, but these errors were encountered: