[otbn] Add functions to classify err_bits
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Different parts of `err_bits` fall into a few different classes
* fatal errors
* software errors
* recoverable errors (currently same as software errors but might not always overlap)
Having some functions such as `is_fatal_err` in `otbn_pkg` can help keep this consistent across everything that needs to take an `err_bits` and classify the kind of error and allow easy alteration of the various classes.
Contributor guide
Research direction
Start in the `otbn_pkg` definitions and trace how `err_bits` is currently interpreted across the project. Identify the fatal, software, and recoverable classifications and the existing users that should share them. Done means consistent classification functions are available in `otbn_pkg` and relevant callers use them, with tests covering the defined classes.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100