From d376b8193fd19cafdf6f951dcba79b5b8aa5b93c Mon Sep 17 00:00:00 2001 From: Franz Fuchs Date: Fri, 6 Dec 2024 10:00:54 +0000 Subject: [PATCH] Did spell checking of cheri-pte-ext chapter --- src/cheri-pte-ext.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/cheri-pte-ext.adoc b/src/cheri-pte-ext.adoc index 8582b3dd..364beb35 100644 --- a/src/cheri-pte-ext.adoc +++ b/src/cheri-pte-ext.adoc @@ -85,9 +85,9 @@ include::img/sv48pte.edn[] [#sv57pte] include::img/sv57pte.edn[] -NOTE: All behaviour related to {cheri_pte_ext_name} requires the authorizing capability to have +NOTE: All behavior related to {cheri_pte_ext_name} requires the authorizing capability to have <>. If <> is _not_ granted then all capability load/stores and AMOs always clear - the tag and the behaviour in this section is not relevant. + the tag and the behavior in this section is not relevant. The CW bit indicates whether reading or writing capabilities with the tag set to the virtual page is permitted. When the CW bit is set, capabilities are written @@ -157,7 +157,7 @@ bit value of the capability read. This will introduce additional traps during re |=== ^1^ The choice here is whether to take data dependent exceptions on loads or atomic operations. - It is legal for the implementation to fault even if the tag is not set since this behaviour is only an optimization for software. + It is legal for the implementation to fault even if the tag is not set since this behavior is only an optimization for software. This means it is also legal to only check the tag under certain conditions and conservatively fault otherwise. ^2^ See <>.