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
Perform the following configurations in HS mode: hvip.vstip=1, hideleg[6]=1, hie.vstie = 1, vsstatus.sie =1. Then excuting sret to VS mode, a VS-level timer interruprt will be excuted and trap to VS mode, but access to sip.stip(really vsip.stip) is read-only at this time, how to clear pending in VS mode without using HS mode (because it is thought that if an ecall instruction is executed in handle for trapping to HS mode, which is considered visible in virtual machine). It confused me.
The text was updated successfully, but these errors were encountered:
The RISC-V Privileged ISA specification, in chapter "Supervisor-Level ISA", subsection "Supervisor Interrupt Registers (sip and sie)", says:
If implemented, STIP is read-only in sip, and is set and cleared by the execution environment.
This statement is modified by extension Sstc, which says
If implemented, STIP is read-only in sip, and is either set and cleared by the execution environment (if stimecmp is not implemented), or reflects the timer interrupt signal resulting from stimecmp (if stimecmp is implemented).
Hence, to clear bit STIP in sip, supervisor-level software must either make an environment call (ECALL) or, if extension Sstc is implemented, write to CSR stimecmp. This is consistently true for all S-level environments, whether S-mode, HS-mode, or VS-mode.
Perform the following configurations in HS mode: hvip.vstip=1, hideleg[6]=1, hie.vstie = 1, vsstatus.sie =1. Then excuting sret to VS mode, a VS-level timer interruprt will be excuted and trap to VS mode, but access to sip.stip(really vsip.stip) is read-only at this time, how to clear pending in VS mode without using HS mode (because it is thought that if an ecall instruction is executed in handle for trapping to HS mode, which is considered visible in virtual machine). It confused me.
The text was updated successfully, but these errors were encountered: