CSR Bit Fields

RISC-V mvip CSR Register

Address 0x309Privilege MachineAccess MRW / 64Machine AIA, timer, and indirect interrupt CSRs

AIA machine virtual interrupt-pending CSR for supervisor-level virtual interrupt state.

Field Map

Understand mvip By Bit Fields

1 key fields
63:0

MVIP

MRW

mvip fields as defined by AIA; detailed bit encoding follows the official AIA specification.

MVIP (bits 63:0) — mvip fields as defined by AIA; detailed bit encoding follows the official AIA specification.

What This Field Controls

  • - mvip fields as defined by AIA; detailed bit encoding follows the official AIA specification.

Common Values

mvip virtual-pending bits
0Not pending

Only for official AIA-defined mvip 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 mvip bits implemented as valid: 1 means the corresponding interrupt is pending; delivery also depends on enable, global interrupt, delegation, virtualization, and interrupt-controller state.

Official Basis & Search Notes

AIA machine virtual interrupt-pending CSR for supervisor-level virtual interrupt state.

The official AIA table lists mvip at 0x309, with MRW access and 64 width.
mvip is a 64-bit machine-level AIA CSR.
This page avoids older generic trap/debug wording.

What To Check First When Reading This CSR

  • - Check mvip address, access class, and width against the official AIA CSR table.
  • - Do not assign fixed meaning to reserved bits or unimplemented interrupt bits.

Risk Checks Before Writing

  • - Modify only target fields and preserve reserved or undefined bits.
  • - Confirm AIA/IMSIC and the relevant supervisor-level support before relying on this CSR.

Put It Back Into A Real Flow

1

Confirm that the hart implements AIA and the relevant component such as S-mode or IMSIC.

2

Read mvip and interpret it according to the AIA definition for virtual interrupts.

3

Use only the listed official fields as portable facts; handle other bits according to the implementation and specification.

FAQ

Is mvip a standard AIA CSR?

Yes. This page follows the address, access class, and width in the official AIA CSR table.

Can unlisted mvip bits be written freely?

No. Reserved, unimplemented, and implementation-defined bits must be handled according to the official specification and implementation requirements.