Tracking issue: improvements to punchthrough
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
The design of the punchthrough has helped us well so far, but I think we've hit its limitations for some time now. Splitting it up into things that are needed for Linux-y shims, things needed for OPTEE-y shims, etc. would likely be the better design. That would make for a less fragile interface, and also help with explaining what's going on in terms of "what do you need from a platform to support this shim".
I've come up with a few alternate designs but they've each had at least some issue along the way, and the punchthrough design that we have is at least a local optima, which is why I haven't actually suggested any changes so far. Nonetheless, it seems helpful to open this issue to track the question.
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
No files, tests, or entry points are named. Start by mapping the existing punchthrough design and the platform requirements for Linux-y and OPTEE-y shims, then compare the alternate designs; done means an agreed, less-fragile interface design is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100