-
Notifications
You must be signed in to change notification settings - Fork 76
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
add a test for user mode #185
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit
32dbff4
to
64bf37b
Compare
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
1 similar comment
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
Tests failed on the main branch so I'm going to see what happened there first, and then check the CI results here. |
336fe77
to
9e48959
Compare
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
Links to coverage and verification reports for this PR (#185) are available at https://chipsalliance.github.io/Cores-VeeR-EL2/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
USER_MODE
in core settings.Currently, riscv-dv doesn't allow specifying privilege modes to be enabled in simulators. There's inconsistence because whisper uses only Machine mode by default, while spike also enables Supervisor and User modes.
With this change, we're explicitly enabling U mode.