[dv, fcov] Look at use of U mode in riscv_mem_intg_error_test
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
We're rarely hitting some bins of priv_mode_irq_cross, though associated with internal NMIs seen in U mode (which occur on ECC errors), increasing test iterations does help but doesn't reliably hit them every regression (https://github.com/lowRISC/ibex/pull/2051)
Investigate why and rework the test to more reliably cover everything without excessive iterations.
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 with the riscv_mem_intg_error_test test and review the coverage bins for priv_mode_irq_cross, especially the U-mode internal NMI cases associated with ECC errors. Compare the behavior and iteration changes discussed in pull request 2051. Done means the relevant bins are reliably hit in regression without excessive test iterations.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100