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
revert(csr): htinst/mtinst should follow the origin spike behaviour
This reverts commit 347cd0e (#33).
According to RISC-V priv spec, htinst/mtinst could be zero when traps into HS/M-mode, except the both following conditions are met:
* the fault is caused by an implicit memory access for VS-stage address translation
* a nonzero value (the faulting guest physical address) is written to mtval2 or htval
Actually, XiangShan would write a nonzero value in such trap, so mtinst could not be written 0.
Acctually, spike only implements this nonzero situation for htinst/mtinst, so no more warps are needed.
0 commit comments