oxidecomputer / oxidecomputer/humility
humility red-light-green-light
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 584
- Forks
- 63
- Avg merge
- 3h
- Merged PRs (30d)
- 2
Description
Actual command name TBD.
Running humility dashboard tends to really screw things up.
This is awesome and I think we should make it much, much worse.
I suspect that the only reason we found https://github.com/oxidecomputer/hubris/issues/544 was because of humility dashboard intermittently halting the CPU, causing the otherwise-high-priority interrupt handling task to effectively be preempted for long periods of time, thereby accumulating flags in its status register in combinations that it would not otherwise see. In other words, this was actually a pretty good driver test.
I propose that we add a command that just randomly halts and resumes the CPU as an exercise for drivers.
Contributor guide
No contributing guide indexed for this repository
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 existing humility dashboard command and the Hubris issue referenced in the report to understand the CPU-halting behavior. The command name and implementation location are not specified; the work is complete when a defined command can randomly halt and resume the CPU as a driver exercise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100