CSR Bit Fields

RISC-V hgeie CSR Register

Address 0x607Privilege HypervisorAccess HRW / HSXLENHypervisor and virtualization CSRs

hgeie is a Hypervisor guest external interrupt-enable CSR.

Field Map

Understand hgeie By Bit Fields

1 key fields
GEILEN:1

GUEST_EXTERNAL_INTERRUPT-ENABLE_BITS

RW

Implemented guest external interrupt-source enable bits in hgeie[GEILEN:1]; only implemented source bits have the 0/1 enable meaning.

GUEST_EXTERNAL_INTERRUPT-ENABLE_BITS (bits GEILEN:1) — Implemented guest external interrupt-source enable bits in hgeie[GEILEN:1]; only implemented source bits have the 0/1 enable meaning.

What This Field Controls

  • - Implemented guest external interrupt-source enable bits in hgeie[GEILEN:1]; only implemented source bits have the 0/1 enable meaning.

Common Values

0Disabled

Only for implemented hgeie[GEILEN:1] bits: the corresponding guest external interrupt source is disabled; unimplemented or other bits follow official WPRI/read-only-zero rules.

1Enabled

Only for implemented hgeie[GEILEN:1] bits: the corresponding guest external interrupt source is enabled; delivery also depends on hstatus.VGEIN and guest external pending state.

Open Official Manual
Official Basis & Search Notes

hgeie is a Hypervisor guest external 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.

hgeie address, access class, and width are checked against the official CSR tables: 0x607, HRW, HSXLEN.
hgeie 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

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

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