oxidecomputer / oxidecomputer/hubris
control-plane-agent: Report reset reason and system time up to MGS
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
We know both the "reason for most recent reset" (available to any task by asking jefe) and the time in ticks since last reset, but neither of these are available without direct humility access. We should make them available via MGS.
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 tracing the control-plane-agent and MGS interfaces, then inspect how jefe exposes the most recent reset reason and how reset-relative ticks are obtained. Done means both the reset reason and system time since reset can be requested through MGS without direct humility access.
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