oxidecomputer / oxidecomputer/hubris
Provide a way of getting a task's index without task-slotting one's self
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
Currently, the testsuite names itself in a task slot.
This is ... not great, because that's what a cycle in the IPC dag would look like. @mkeeter has added an exemption in our priority inversion scans for this case. I'd like to remove it eventually because it might mask bugs.
The reason testsuite task-slots itself is to get its task index. That value is available at build time (by definition) and we could provide a way of getting at it -- a way that doesn't look like an interaction bug.
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 with the testsuite setup that task-slots itself to obtain its task index, then inspect the priority inversion scan exemption mentioned in the issue. The change is complete when testsuite can access its build-time task index without creating an IPC DAG cycle and the special exemption is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100