CSR Bit Fields

RISC-V hie CSR Register

Address 0x604Privilege HypervisorAccess HRW / HSXLENHypervisor and virtualization CSRs

hie is a Hypervisor interrupt-enable CSR.

Field Map

Understand hie By Bit Fields

1 key fields
HSXLEN-1:0

HYPERVISOR_INTERRUPT-ENABLE_BITS

RW

The hypervisor interrupt-enable bits of hie; only officially defined hypervisor interrupt-enable bits have fixed 0/1 enable meaning.

HYPERVISOR_INTERRUPT-ENABLE_BITS (bits HSXLEN-1:0) — The hypervisor interrupt-enable bits of hie; only officially defined hypervisor interrupt-enable bits have fixed 0/1 enable meaning.

What This Field Controls

  • - The hypervisor interrupt-enable bits of hie; only officially defined hypervisor interrupt-enable bits have fixed 0/1 enable meaning.

Common Values

0Disabled

Only for officially defined Hypervisor/VS-level interrupt-enable bits: 0 means that interrupt is disabled; reserved or undefined bits have no fixed enable meaning.

1Enabled

Only for officially defined Hypervisor/VS-level interrupt-enable bits: 1 means that interrupt is enabled; delivery also depends on pending state and delegation/virtualization state. Reserved or undefined bits have no fixed enable meaning.

Open Official Manual
Official Basis & Search Notes

hie is a Hypervisor interrupt-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.

hie address, access class, and width are checked against the official CSR tables: 0x604, HRW, HSXLEN.
hie fields are interpreted by the corresponding Hypervisor extension section; unimplemented fields must not be treated as fixed writable bits.
When writing, modify only officially defined fields; handle WARL, WLRL, WPRI, and reserved fields according to the official specification and implementation behavior.

What To Check First When Reading This CSR

  • - hie 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 hie, 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 hie be accessed through a supervisor CSR alias?

Do not treat hie 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.