oxidecomputer / oxidecomputer/hubris
Kernel syscall argument handling is too boilerplatey
Open
Nobody has claimed this yet.
kernel
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
The AsFooArgs structs in kern/src/task.rs were my first attempt at having an abstraction layer in syscall argument handling, to insulate most of the code from architecture and ABI changes. They work but adding a syscall requires kind of a lot of typing.
I bet we could make this simpler.
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
Start by reading the AsFooArgs structs and surrounding syscall argument handling in kern/src/task.rs, then trace how architecture and ABI changes are insulated. Done means adding a syscall requires substantially less boilerplate while preserving that abstraction layer; the issue does not name a test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100