[rtl, doc] Consider hardening data_rvalid_i for 2-stage config
Open
Nobody has claimed this yet.
Component:Doc
Component:RTL
Type:Enhancement
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
PR lowRISC/Ibex#1968 adds some little extra hardening around data_rvalid_i for the WB-stage configuration used in OpenTitan.
We should probably think whether:
- We can port this extra protection over to the 2-stage configuration.
- How to best document this extra hardening not controllable with the
SecureIbexparameter as other countermeasures in case it indeed turns out that the porting cannot be easily done or isn't worth the effort.
For details, refer to https://github.com/lowRISC/ibex/pull/1968#issuecomment-1377193487.
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 reading the hardening changes and discussion in lowRISC/Ibex#1968, then trace how data_rvalid_i is handled in the 2-stage configuration and compare it with the WB-stage configuration used in OpenTitan. Done means deciding whether the protection can be ported and, if not, documenting the extra hardening and its relationship to the SecureIbex parameter.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100