RISC-V hvip CSR Register

Address 0x645Privilege HypervisorAccess HRW / 64-bitHypervisor and virtualization CSRs

hvip is a virtual interrupt-pending bitmap for VS injection.

Related Search Terms

hvip CSR hvip 0x645 RISC-V AIA virtual interrupt pending virtual interrupt

Bit Overview

Hover for details · Click to jump↗Open Official Manual

bit 3 = only bit 3; bits 12..11 = bits 12 down to 11

MSBLSB

HVIP63:0RW

Field Map

Understand hvip By Bit Fields

1 key fields

63:0

HVIP

hvip fields for virtual interrupt pending; detailed encoding follows the AIA specification.

HVIP (bits 63:0) — hvip fields for virtual interrupt pending; detailed encoding follows the AIA specification.

What This Field Controls

- hvip fields for virtual interrupt pending; detailed encoding follows the AIA specification.

Common Values

hvip virtual pending bits

0Not pending

Only for official AIA-defined hvip virtual-interrupt pending bits implemented as valid: 0 means the corresponding interrupt is not pending; reserved, undefined, or unimplemented bits do not have this fixed meaning.

1Pending

Only for official AIA-defined hvip virtual-interrupt pending bits implemented as valid: 1 means the corresponding interrupt is pending; delivery also depends on enable, global interrupt, delegation, virtualization, and interrupt-controller state.

↗Open Official Manual

Official Basis & Search Notes

hvip is an AIA virtual-interrupt 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.

hvip address, access class, and width are checked against the official CSR tables: 0x645, HRW, 64-bit.

AIA defines hypervisor virtual-interrupt CSRs that augment hvip for injecting interrupts into VS level.

Exact fields and priority encoding are interpreted by the AIA VS-level interrupt rules.

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 table RISC-V Advanced Interrupt Architecture CSR chapter RISC-V AIA VS-level interrupts

What To Check First When Reading This CSR

- hvip 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 hvip, modify only officially defined target fields and preserve WPRI, reserved, and unchanged fields.

Put It Back Into A Real Flow

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

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

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

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

Can state-enable CSRs control access to hvip?

When Smstateen and AIA are implemented, AIA, IMSIC, or CSRIND bits in mstateen0/hstateen0 may control lower-privilege or VM access to related AIA state.