From 403b739541540af1101ee29dac9cb1f6a4f9d9e8 Mon Sep 17 00:00:00 2001
From: lkcl <lkcl@web>
Date: Sat, 15 Jun 2019 07:04:50 +0100
Subject: [PATCH]

---
 isa_conflict_resolution/isamux_isans.mdwn | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/isa_conflict_resolution/isamux_isans.mdwn b/isa_conflict_resolution/isamux_isans.mdwn
index e3da945b3..e651b7f1f 100644
--- a/isa_conflict_resolution/isamux_isans.mdwn
+++ b/isa_conflict_resolution/isamux_isans.mdwn
@@ -89,17 +89,18 @@ To be discussed. Context <https://groups.google.com/a/groups.riscv.org/d/msg/isa
 
 An additional WLRL CSR per priv-level named "LAST-ISANS" is required, and
 another called "TRAP-ISANS"
-These mirrors the ISANS CSR, and, on a trap, if the current ISANS in
-that privilege level is not equal to TRAP-ISANS, its value is atomically
+These mirrors the ISANS CSR, and, on a trap, the current ISANS in
+that privilege level is atomically
 transferred into LAST-ISANS by the hardware, and ISANS in that trap
 is set to TRAP-ISANS.  Hardware is *only then* permitted to modify the PC to
 begin execution of the trap.
 
-On exit from the trap, hardware must check to see if LAST-ISANS is equal
-to TRAP-ISANS.  If it is not, LAST-ISANS is copied into the ISANS CSR,
-LAST-ISANS is set to TRAP-ISANS, and *only then* is the hardware permitted
+On exit from the trap, LAST-ISANS is copied into the ISANS CSR, and
+LAST-ISANS is set to TRAP-ISANS. *Only then* is the hardware permitted
 to modify the PC to begin execution where the trap left off.
 
+This is identical to how xepc is handled.
+
 Note 1: in the case of Supervisor Mode (context switches in particular),
 saving and changing of LAST-ISANS (to and from the stack) must be done
 atomically and under the protection of the SIE bit.  Failure to do so
-- 
2.30.2