From fc41db64f3cf618534adf02422db1ea4deb3ce4f Mon Sep 17 00:00:00 2001
From: Andrew Waterman <andrew@sifive.com>
Date: Sun, 2 Dec 2018 22:15:02 -0800
Subject: WIP on M-mode chapter

---
 src/priv-intro.tex | 12 ------------
 1 file changed, 12 deletions(-)

(limited to 'src/priv-intro.tex')

diff --git a/src/priv-intro.tex b/src/priv-intro.tex
index 723b9b4..7787f69 100644
--- a/src/priv-intro.tex
+++ b/src/priv-intro.tex
@@ -142,18 +142,6 @@ manage secure execution environments on RISC-V.  User-mode (U-mode)
 and supervisor-mode (S-mode) are intended for conventional application
 and operating system usage respectively.
 
-\begin{commentary}
-The previous Hypervisor mode (H-mode) designed to support Type-1
-hypervisors has been removed and the encoding space reserved as we are
-focusing on hypervisor support via an extended S mode suitable for
-both Type-1 and Type-2 hypervisors as described in
-Chapter~\ref{hypervisor}.  The encoding space for H is reserved for
-future use and to avoid backwards incompatible changes in bit
-positions in various status registers.  The bit positions might be
-reused in the future for different Type-1 hypervisor support or
-possibly additional secure execution modes.
-\end{commentary}
-
 Each privilege level has a core set of privileged ISA extensions with optional
 extensions and variants.  For example, machine-mode supports an optional
 standard extension for memory protection.  Also, supervisor mode can be
-- 
cgit v1.1

