From 477615e31a756582d1fee56b09f1d1aacf8391ee Mon Sep 17 00:00:00 2001 From: Ravi Sahita Date: Wed, 2 Oct 2024 13:49:48 -0700 Subject: [PATCH] SDID unique to a hart scope Signed-off-by: Ravi Sahita --- chapter3.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapter3.adoc b/chapter3.adoc index 0833151..bdc9791 100644 --- a/chapter3.adoc +++ b/chapter3.adoc @@ -9,7 +9,7 @@ hart and may be used to tag hart-local resources to access-control data associated with the supervisor domain. For most typical usages, the SDID will remain stable over the life of the supervisor domain. However, the SDID can be changed at the cost of fencing to flush any prior cached state. The SDID is -unique only within a cpu-complex, hence, SDID must not be used to tag downstream +unique only to a hart, hence, SDID must not be used to tag downstream transactions that are globally visible - implementations may map the SDID from the initiator to other (global) identifiers but that mapping is implementation-specific and out of scope of this specification.