You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The section "smclicshv Changes to Next Interrupt Handler Address and Interrupt-Enable
CSRs (xnxti)" modifies the behaviour of immediate version of xnxti, but doesn't clearly state how register version should behave
Now there are multiple possible interpretations of the xnxti register version's behaviour.
1, The register version behaves as defined in " Next Interrupt Handler Address and Interrupt-Enable CSRs (xnxti)"
2, The register version behaves the same as immediate version
3, The register version contains the original difference in clic.level comparison (clic.level > rs1[23:16]) while returning zero when the incoming interrupt is hardware vectored.
The option 3, seems to be the intended one.
Can the difference between register and immediate version get clear definition in smclicshv?
The text was updated successfully, but these errors were encountered:
The section "smclicshv Changes to Next Interrupt Handler Address and Interrupt-Enable
CSRs (xnxti)" modifies the behaviour of immediate version of xnxti, but doesn't clearly state how register version should behave
Now there are multiple possible interpretations of the xnxti register version's behaviour.
1, The register version behaves as defined in " Next Interrupt Handler Address and Interrupt-Enable CSRs (xnxti)"
2, The register version behaves the same as immediate version
3, The register version contains the original difference in
clic.level
comparison (clic.level > rs1[23:16]) while returning zero when the incoming interrupt is hardware vectored.The option 3, seems to be the intended one.
Can the difference between register and immediate version get clear definition in smclicshv?
The text was updated successfully, but these errors were encountered: