RVOPcode
Back To CSR WorkbenchView In Register Browser
CSR Bit Fields

RISC-V utvt CSR Register

Address 0x007Privilege UserAccess RW / 32Reserved, custom, or uncategorized CSRs

utvt at 0x007 is a AIA/N extension CSR: is a standard named CSR in the AIA/N extension category. (Compatibility entry for legacy or non-current ratified base privileged specifications; confirm the source extension before use.)

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

Understand utvt By Bit Fields

1 key fields
XLEN-1:0

VALUE

RW

Full register value of utvt; bits not split out here follow the relevant extension or privileged specification, and reserved or WPRI fields should be preserved when writing other fields and ignored on reads.

VALUE (bits XLEN-1:0) — Full register value of utvt; bits not split out here follow the relevant extension or privileged specification, and reserved or WPRI fields should be preserved when writing other fields and ignored on reads.

What This Field Controls

  • - Full register value of utvt; bits not split out here follow the relevant extension or privileged specification, and reserved or WPRI fields should be preserved when writing other fields and ignored on reads.

Common Values

This field is better understood together with surrounding context than as a fixed memorized enumeration.

↗Open Official Manual

What To Check First When Reading This CSR

  • - First confirm that the current hart implements utvt; unimplemented or insufficiently privileged accesses raise an illegal-instruction exception.
  • - Use address 0x007 and the lowest access privilege (User) to decide whether software may read it directly.
  • - Do not assume fixed values for reserved, WARL, or WLRL bits; interpret the value according to the specification and implementation.

Risk Checks Before Writing

  • - Preserve bits that are not being changed so reserved or implementation-defined fields are not written with invalid values.
  • - Prefer CSRRS/CSRRC for local set/clear operations to avoid CSRRW overwriting concurrently updated status bits.

Put It Back Into A Real Flow

1

During initialization or the relevant privileged flow, software reads utvt to observe the current state.

2

Modify only the target fields while preserving all other bits.

3

Read back the CSR or validate through later trap, interrupt, or context-switch behavior that the setting took effect.