From 98da12d09a74dfbb0abdc50088e58691f221fb7e Mon Sep 17 00:00:00 2001
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date: Fri, 14 Jun 2019 07:50:12 +0100
Subject: [PATCH] add TRAP-ISANS

---
 isa_conflict_resolution/isamux_isans.mdwn | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/isa_conflict_resolution/isamux_isans.mdwn b/isa_conflict_resolution/isamux_isans.mdwn
index b5d24f076..9504ce123 100644
--- a/isa_conflict_resolution/isamux_isans.mdwn
+++ b/isa_conflict_resolution/isamux_isans.mdwn
@@ -95,6 +95,9 @@ written into LAST-ISANS occur when the *software* writes to LAST-ISANS,
 or when the *trap* (on exit) writes into LAST-ISANS?  this latter seems
 fraught: a trap, on exit, causing another trap??
 
+Per-privilege-level pseudocode (there exists UISANS, UTRAPISANS, ULASTISANS,
+MISANS, MTRAPISANS, MLASTISANS and so on):
+
 <code>
 <pre>
 trap_entry()
-- 
2.30.2