RVOPcode
Back To CSR WorkbenchView In Register Browser
CSR Bit Fields

RISC-V vsctrctl CSR Register

Address 0x24EPrivilege Hypervisor direct / VS aliasAccess HRW / VSXLENHypervisor and virtualization CSRs

vsctrctl is the VS copy of the Control Transfer Records control CSR.

Related Search Terms
vsctrctl CSRvsctrctl 0x24EVS CTR controlCTR CSRdirect HRW access
Bit Overview
bit 3 = only bit 3; bits 12..11 = bits 12 down to 11
MSBLSB
CTRCTL63:0RW
Field Map

Understand vsctrctl By Bit Fields

1 key fields
VSXLEN-1:0

CTRCTL

RW

VS Control Transfer Records control fields; exact fields are interpreted by the CTR extension.

CTRCTL (bits VSXLEN-1:0) — VS Control Transfer Records control fields; exact fields are interpreted by the CTR extension.

What This Field Controls

  • - VS Control Transfer Records control fields; exact fields are interpreted by the CTR extension.

Common Values

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

↗Open Official Manual
Official Basis & Search Notes

vsctrctl is a VS CTR control CSR. The separate CSR address is for M/HS-side management; when V=1, a guest reaches VS CTR state through the corresponding supervisor alias.

vsctrctl address, access class, and width are checked against the official CSR tables: 0x24E, HRW, VSXLEN.
It belongs to Control Transfer Records control state, not ordinary trap or interrupt state.
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 tableRISC-V Privileged Architecture Manual - Hypervisor extension

What To Check First When Reading This CSR

  • - vsctrctl's separate CSR address is in the official HRW access class; a VS/VU guest normally reaches VS state through the corresponding supervisor CSR alias.
  • - Before reading it, confirm that the CTR-related extension is implemented.

Risk Checks Before Writing

  • - When writing vsctrctl, modify only officially defined CTR control fields and preserve WPRI, reserved, and unchanged fields.

Put It Back Into A Real Flow

1

Confirm the CTR and H extensions are implemented.

2

M/HS software manages the VS copy through the separate CSR address.

3

A guest reaches VS CTR state through the corresponding supervisor CSR alias.

FAQ

How is vsctrctl related to the CTR extension?

It is VS-level CTR control state; interpret its fields only when the related CTR state is implemented.

Can VS-mode directly access the separate vsctrctl address?

No. A VS/VU guest reaches the VS copy through the corresponding supervisor alias; direct access to the separate VS CSR address raises a virtual-instruction exception.