Ask a question related to Ibex
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
I tried running Ibex small configuration with different workload by turning the Icache parameter on and off (assigning it 0 and 1) this is what I got in the Simulation statistics
Without Cache
Simulation statistics
Executed cycles: 167525
Wallclock time: 8.708 s
Simulation speed: 19238.1 cycles/s (19.2381 kHz)
Trace file size: 5758073 B
With cache
Simulation statistics
Executed cycles: 167525
Wallclock time: 14.255 s
Simulation speed: 11752 cycles/s (11.752 kHz)
Trace file size: 7273683 B
I tested it with different workloads and different configurations available in ibex. it seems like the Executed cycles should be smaller if a cache exists. On top of that it seems the wallclock time takes longer for a configuration with cache.
I also tried decreasing the clock from 0.5 to 0.05 in ibex_simple_system.sv but still the Executed cycles do not change.
My Environment
I am using wsl on windows and I am running ibex simple system on bare metal
I am using ubuntu Ubuntu 22.04.4 LTS
EDA tool and version:
Operating system:
Version of the Ibex source code:
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 ibex_simple_system.sv and the small configuration's Icache setting, reproducing the reported cache-on and cache-off simulation statistics. Record the Ibex source revision, exact workloads and configurations, and the clock setting; done means explaining whether the differing wallclock time and unchanged executed cycles are expected or indicate a defect.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100