oasisprotocol / oasisprotocol/oasis-core
Callgrind mapping
Open
Nobody has claimed this yet.
c:testing
p:3
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Find out where enclave is loaded at runtime.
Get the callgrind annotator to apply mapping.
Currently callgrind cannot find enclave in simulation mode.
Used for no-SGX profiling
an enclave can get its own location with &__ImageBase: https://github.com/intel/linux-sgx/blob/master/sdk/trts/trts.cpp#L72
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace how the enclave is loaded in simulation mode and where the callgrind annotator applies mappings. Read the referenced SDK file, sdk/trts/trts.cpp, for the __ImageBase location approach. Done means callgrind can locate and annotate the enclave during no-SGX profiling.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100