CSR Bit Fields

RISC-V hgeip CSR Register

Address 0xE12Privilege HypervisorAccess HRO / HSXLENHypervisor and virtualization CSRs

hgeip is a Hypervisor guest external interrupt-pending CSR.

Bit Overview
bit 3 = only bit 3; bits 12..11 = bits 12 down to 11
MSBLSB
Field Map

Understand hgeip By Bit Fields

1 key fields
HSXLEN-1:1

GUEST_EXTERNAL_INTERRUPT-PENDING_BITS

RO

The guest external interrupt-pending bits of hgeip.

GUEST_EXTERNAL_INTERRUPT-PENDING_BITS (bits HSXLEN-1:1) — The guest external interrupt-pending bits of hgeip.

What This Field Controls

  • - The guest external interrupt-pending bits of hgeip.

Common Values

implemented GEILEN source bit
0Not pending

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

1Pending

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

Open Official Manual
Official Basis & Search Notes

hgeip is a Hypervisor guest external interrupt-pending 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.

hgeip address, access class, and width are checked against the official CSR tables: 0xE12, HRO, HSXLEN.
hgeip fields are interpreted by the corresponding Hypervisor extension section; unimplemented fields must not be treated as fixed writable bits.
hgeip is read-only; reserved or implementation-defined read values should be interpreted only as the official specification and implementation define them.

What To Check First When Reading This CSR

  • - hgeip is a Hypervisor-level CSR; its separate address is in the official HRO 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

  • - hgeip is read-only; software should not write it.

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

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