oxidecomputer / oxidecomputer/propolis
MSRs need better handling
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
(Read: literally any handling)
Out of expedience, we've just been punting on unhandled MSRs up until now, simply logging errors about them and doing the bare minimum to move past them (either quietly accepting the wrmsr, or returning 0 for the rdmsr). This is going to backfire sooner rather than later, so we should get a better story together for their handling.
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 tracing the existing handling of unhandled MSRs, focusing on the wrmsr and rdmsr paths described in the issue and their error logging. Define the desired behavior for unsupported reads and writes, then verify that the resulting handling no longer relies on silently accepting writes or returning 0 for reads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100