lowRISC / lowRISC/opentitan

[dv,rstmgr] Generate list of rstmgr_leaf_rst instances

Open
#13,640 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component:MultiTop Earlgrey-PROD Candidate IP:rstmgr Priority:P3
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

The rstmgr_leaf_rst_cnsty and rstmgr_leaf_rst_shadow_attack countermeasure tests rely on the LIST_OF_LEAFS and LIST_OF_SHADOW_LEAFS lists of instances of rstmgr_leaf_chk instances in rstmgr, declared in rstmgr_env_pkg.sv.

If the names of these instances changes these tests will start failing, but if a new instance is added there will be no test failures but the countermeasures for the missing instances won't be tested.

We could auto-generate these lists, or create some other check to detect out-of-date lists.

estimate 8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with rstmgr_env_pkg.sv and the rstmgr_leaf_rst_cnsty and rstmgr_leaf_rst_shadow_attack countermeasure tests, focusing on LIST_OF_LEAFS and LIST_OF_SHADOW_LEAFS. Determine how the instance lists can stay synchronized or detect missing instances; done means renamed or newly added rstmgr_leaf_chk instances cannot leave the countermeasure tests out of date.

Written by the indexing model from the issue text.

Assessment

Domain
security, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.