Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are Zicntr tests meaningful in lockstep? #523

Open
jordancarlin opened this issue Mar 8, 2025 · 1 comment
Open

Are Zicntr tests meaningful in lockstep? #523

jordancarlin opened this issue Mar 8, 2025 · 1 comment

Comments

@jordancarlin
Copy link
Member

All of the counter CSRs are set as volatile, which means the reference model will just return whatever the DUT says for each of them. This means any reads or writes we do to them will appear to be successful no matter what actually happens.

This is an issue for cycle, mcycle, instret, minstret, time, hpmcounterx, mhpmcounterx, and the h versions of each of these CSRs.

@jordancarlin
Copy link
Member Author

MIP and SIP are also set as volatile, but I think this should be ok with how we are testing interrupts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant