aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBill Traynor <wmat@riscv.org>2023-03-22 14:47:51 -0400
committerBill Traynor <wmat@riscv.org>2023-03-22 14:47:51 -0400
commitd282be168046b0c393123138fbab4be5e602d2bc (patch)
treebdc370952e3740669425a54ede763814485741a9
parentebf9e9d29ff1e5ecf7051a886e5ebf177cdf0d45 (diff)
downloadriscv-isa-manual-d282be168046b0c393123138fbab4be5e602d2bc.zip
riscv-isa-manual-d282be168046b0c393123138fbab4be5e602d2bc.tar.gz
riscv-isa-manual-d282be168046b0c393123138fbab4be5e602d2bc.tar.bz2
Added admonition
Added missing admonition
-rw-r--r--src/hypervisor.adoc3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/hypervisor.adoc b/src/hypervisor.adoc
index 6e717a8..8c59a27 100644
--- a/src/hypervisor.adoc
+++ b/src/hypervisor.adoc
@@ -818,6 +818,8 @@ effect. Attempts to execute a floating-point instruction when either
field is 0 (Off) raise an illegal-instruction exception. Modifying the
floating-point state when V=1 causes both fields to be set to 3 (Dirty).
+[NOTE]
+====
For a hypervisor to benefit from the extension context status, it must
have its own copy in the HS-level `sstatus`, maintained independently of
a guest OS running in VS-mode. While a version of the extension context
@@ -828,6 +830,7 @@ VS-level software can change `vsstatus`.FS arbitrarily. If the HS-level
hardware in parallel with `vsstatus`.FS while V=1, hypervisors would
always be forced to conservatively swap all floating-point state when
context-switching between virtual machines.
+====
Similarly, when V=1, both `vsstatus`.VS and the HS-level `sstatus`.VS
are in effect. Attempts to execute a vector instruction when either