RVOPcode
Back To CSR WorkbenchView In Register Browser
CSR Bit Fields

RISC-V hcontext CSR Register

Address 0x6A8Privilege HypervisorAccess HRW / HSXLENHypervisor and virtualization CSRs

hcontext is a Hypervisor context CSR.

Related Search Terms
hcontext CSRhcontext 0x6A8hypervisor context value for debug/traceHypervisor
Bit Overview
bit 3 = only bit 3; bits 12..11 = bits 12 down to 11
MSBLSB
HYPERVISOR_CONTEXT_VALUE_FOR_DEBUG/TRACE63:0RW
Field Map

Understand hcontext By Bit Fields

1 key fields
HSXLEN-1:0

HYPERVISOR_CONTEXT_VALUE_FOR_DEBUG/TRACE

RW

The hypervisor context value for debug/trace of hcontext.

HYPERVISOR_CONTEXT_VALUE_FOR_DEBUG/TRACE (bits HSXLEN-1:0) — The hypervisor context value for debug/trace of hcontext.

What This Field Controls

  • - The hypervisor context value for debug/trace of hcontext.

Common Values

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

↗Open Official Manual
Official Basis & Search Notes

hcontext is a Hypervisor context 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.

hcontext address, access class, and width are checked against the official CSR tables: 0x6A8, HRW, HSXLEN.
hcontext fields are interpreted by the corresponding Hypervisor extension section; unimplemented fields must not be treated as fixed writable bits.
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

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

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

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