lowRISC / lowRISC/opentitan

[rtl,pwrmgr] escalation reset requests should not be delayed so much

Open
#20,518 9 comments 0 reactions 3 assignees View on GitHub

Nobody has claimed this yet.

Component:Doc Component:Security Earlgrey-PROD Candidate IP:pwrmgr Priority:P2 Security: SW Guidance Type:FutureRelease
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

### Description

The reset requests to pwrmgr go through aon clk synchronizers. This seems problematic for escalation resets, given they are more security critical, since it leaves a window of hundreds of cycles after the escalation cause when the cpu remains active.

Below there is a proposed way to block cpu fetching, and this issue will require two items:
- [ ] Add support to disable cpu fetch upon escalation request reception
- [ ] Add unit test for this feature

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.