(no commit message)

diff --git a/openpower/sv/rfc/001.mdwn b/openpower/sv/rfc/001.mdwn
index 246f14e0660d147ed0f9fd53aba166d17af5d668..dfb52509d1775dbe189654e40702cd8878796e7a 100644 (file)
--- a/openpower/sv/rfc/001.mdwn
+++ b/openpower/sv/rfc/001.mdwn
@@ -5,6 +5,7 @@
 Links
 
 * <https://libre-soc.org/openpower/sv/>
+* <https://libre-soc.org/openpower/sv/compliancy_levels/>
 * <https://libre-soc.org/openpower/transcendentals/>
 * <https://libre-soc.org/openpower/sv/bitmanip>
 * <https://libre-soc.org/openpower/sv/int_fp_mv>
@@ -42,6 +43,27 @@ AMD and many other ISAs have been adding over the past 12 years.
 *Thus it becomes necesary to consider the Architectural Resource Allocation of not just
 Simple-V but the 80-100 Scalar instructions all at the same time*.
 
-# Resources
+It is also critical to note that Simple-V **does not modify the Scalar Power ISA
+in any way**. There is one sole semi-exception to that (Vectorised Branch Conditional)
+in order to provide the usual capability present in every Commercial 3D GPU ISA.
 
+# Compliancy Levels
+
+Simple-V has been subdivided into levels akin to the Power ISA Compliancy Levels.
+For now Let us call them "SV Compliancy Levels" to distinguish the two.  The reason for
+the SV Compliancy Levels is the same as for the Power ISA Compliancy Levels (SFFS, SFS):
+to not overburden implementors with features that they do not need.
+*There is no dependence between the two types of Compliancy Levels*
+
+The resources below therefore are not all required for all SV Compliancy Levels but
+they are all required
+
+# Simple-V Resources
+
+* No new Interrupt types are required.
+* Register numbers are extended to 128 (including CR Fields).
+  A future version may extend to 256 or beyond [^extend]
+
+
+[^extend]: Prefix opcode space **must** be reserved in advance to to so, in order to avoid the catastrophic mistake made by RISC-V RVV and ARM SVE/2