RVOPcode
Back To CSR WorkbenchView In Register Browser
CSR Bit Fields

RISC-V hstateen3h CSR Register

Address 0x61FPrivilege HypervisorAccess HRW / 32-bit RV32 high halfHypervisor and virtualization CSRs

hstateen3h is the RV32 high half of hypervisor state-enable CSR.

Related Search Terms
hstateen3h CSRhstateen3h 0x61Fhstateen state enablestate enable bitsSmstateen
Bit Overview
bit 3 = only bit 3; bits 12..11 = bits 12 down to 11
MSBLSB
Field Map

Understand hstateen3h By Bit Fields

0 key fields
Official Basis & Search Notes

hstateen3h is a hypervisor state-enable CSR. It is HS/M-side hypervisor state, not a VS supervisor CSR copy; guest access is governed by the H extension and relevant state-enable, AIA, Sstc, or Smcsrind rules.

hstateen3h address, access class, and width are checked against the official CSR tables: 0x61F, HRW, 32-bit RV32 high half.
State-enable CSRs control lower-privilege or VM access to extension state; they do not affect M-mode access.
hstateen1-3 bits are allocated by official extensions; unallocated bits must not be treated as ordinary VALUE.
When writing, modify only officially defined fields; handle WARL, WLRL, WPRI, and reserved fields according to the official specification and implementation behavior.
RISC-V Privileged Architecture Manual - CSR tableRISC-V Privileged Architecture Manual - Hypervisor extensionRISC-V Smstateen/Ssstateen extensionRISC-V Advanced Interrupt Architecture CSR chapterRISC-V Smcsrind/Sscsrind indirect CSR extension

What To Check First When Reading This CSR

  • - hstateen3h is a Hypervisor-level CSR; its separate address is in the official HRW access class.
  • - Guest/VS software does not reach this H-level CSR through a supervisor CSR alias; access is controlled by the H extension and relevant optional-extension rules.

Risk Checks Before Writing

  • - When writing hstateen3h, modify only officially defined target fields and preserve WPRI, reserved, and unchanged fields.

Put It Back Into A Real Flow

1

Confirm the current software is in an M/HS context that may access Hypervisor CSRs.

2

Confirm that the H, AIA, Sstc, Smstateen, Smcsrind, or other defining extension is implemented.

3

Read or write only official fields; whether guest-related access succeeds or traps is controlled by the corresponding extension rules and state-enable state.

FAQ

Can hstateen3h be accessed through a supervisor CSR alias?

Do not treat hstateen3h as a VS CSR copy. It is an H-level CSR; whether guest/VS access to related functionality traps is defined by the H extension and the relevant optional extension.

What do the AIA/IMSIC/CSRIND bits in hstateen0 control?

They control VM access to AIA, guest IMSIC, and indirect CSR alias state, respectively.