lowRISC / lowRISC/ibex

Report traps and privilege level in trace

Open
#2,334 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
SystemVerilog
Stars
2.1k
Forks
810
Avg merge
5d 23h
Merged PRs (30d)
9

Description

There are a few signals in the tracer module that aren't printed to the output file:

```
// These signals are part of RVFI, but not used in this module currently.
// Keep them as part of the interface to change the tracer more easily in the future. Assigning
// these signals to unused_* signals marks them explicitly as unused, an annotation picked up by
// linters, including Verilator lint.
logic [63:0] unused_rvfi_order = rvfi_order;
logic unused_rvfi_trap = rvfi_trap;
logic unused_rvfi_halt = rvfi_halt;
logic unused_rvfi_intr = rvfi_intr;
logic [ 1:0] unused_rvfi_mode = rvfi_mode;
logic [ 1:0] unused_rvfi_ixl = rvfi_ixl;
```

It would be *really* helpful if there was an extra column for the current privilege, and for traps to be printed.

If I make a PR for this would it be accepted?

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 by locating the tracer module and its output-file format, then inspect the RVFI signals listed in the issue, especially rvfi_trap and rvfi_mode. The change is complete when trace output includes the current privilege level and trap information, with relevant tracer tests or checks updated if present.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.