From 98a11f5855af026d568a7a25ff68b5117446994b Mon Sep 17 00:00:00 2001 From: Tariq Kurd Date: Fri, 6 Dec 2024 11:30:56 +0000 Subject: [PATCH] Update src/riscv-integration.adoc Co-authored-by: Nathaniel Wesley Filardo Signed-off-by: Tariq Kurd --- src/riscv-integration.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/riscv-integration.adoc b/src/riscv-integration.adoc index b3f551c1..ab0ca562 100644 --- a/src/riscv-integration.adoc +++ b/src/riscv-integration.adoc @@ -1198,9 +1198,9 @@ Some situations may appear to require that the CSR come to hold a capability wit * hardware updates to CSRs such as storing the <> (which becomes capability A) into <>/<> etc. when taking an exception. -The procedure is: +In order to satisfy the definitions of such CSRs and preserve capability system invariants, the following procedure must be used as part of write-back to the CSR: -. If A's address is invalid, A does not have infinite bounds (see +. If A's address is invalid and A does not have infinite bounds (see xref:section_cap_encoding[xrefstyle=short]), then A's tag is set to 0. . Write the final (potentially modified) version of capability A to the CSR e.g. <>, <>, etc.