When is execution legal?
At the supported XLEN, with H implemented: M/HS or V=0 U-mode with HU=1 may execute. V=0 U-mode with HU=0 raises illegal-instruction; V=1 raises virtual-instruction.
Hypervisor virtual-machine store of a byte using VS/VU effective privilege and two-stage translation.
Extension condition: H extension 1.0; RV32/RV64. V=0, in M/HS or U-mode with hstatus.HU=1.
HSV.B is the H-extension virtual-machine store. It may execute in M-mode or HS-mode, or in U-mode when hstatus.HU=1. The explicit memory access uses effective privilege VU when hstatus.SPVP=0 and VS when hstatus.SPVP=1, with two-stage address translation.
Shows HSV.B SYSTEM decoding, privilege checks, two-stage translation, and 8-bit store commitment without modeling page walks or TLB implementation.
Assumes H is implemented, relevant privilege modes use the same XLEN, and pointer masking is disabled. Input represents low source bits; the selector supplies the access outcome without validating page tables. rs1=x0 fixes address zero. Steps are teaching stages, not processor cycles.
rs2=x0 fixes the source to zero. With rs1=rs2, source low bits derive from the same address register and cannot be edited independently. Both use pre-execution values. The stored number represents the full access width; byte endianness is not simulated.
This animation shows only official architectural conditions and outcomes; page walks, TLBs, caches, and platform exception handling are not modeled.
Address=rs1 (no offset). Success: store rs2[7:0] to memory; no rd write.
RV64 H, HS-mode, SPVP=0, pointer masking off, address 0x1000 and a successful access: a0=0x1000 and a1=0x1234; hsv.b a1, (a0) writes 0x34 to 8 bytes at that address.
At the supported XLEN, with H implemented: M/HS or V=0 U-mode with HU=1 may execute. V=0 U-mode with HU=0 raises illegal-instruction; V=1 raises virtual-instruction.