(no commit message)

diff --git a/openpower/sv/remap.mdwn b/openpower/sv/remap.mdwn
index bd2c0ff2a36f8b2c44a976b990e3cef7a5010b0c..45407b2acc55496dde40ae2610bc988dc561ca09 100644 (file)
--- a/openpower/sv/remap.mdwn
+++ b/openpower/sv/remap.mdwn
@@ -77,6 +77,12 @@ for *possible* latency alone.  Commonly-used patterns such as Matrix
 Multiply, DCT and FFT have helper instruction options which make REMAP
 easier to use.
 
 Multiply, DCT and FFT have helper instruction options which make REMAP
 easier to use.
 

+*Future specification note: future versions of the REMAP Management instructions
+will extend to EXT1xx Prefixed variants. This will overcome some of the limitations
+present in the 32-bit variants of the REMAP Management instructions that at
+present require direct writing to SVSHAPE0-3 SPRs.  Additional
+REMAP Modes may also be introduced at that time.*
+

 There are four types of REMAP:
 
 * **Matrix**, also known as 2D and 3D reshaping, can perform in-place
 There are four types of REMAP:
 
 * **Matrix**, also known as 2D and 3D reshaping, can perform in-place


@@ -114,12 +120,6 @@ it is possible to service Precise Interrupts without affecting latency
 Parallel Reduction instructions, because their Architectural State cannot
 hold the partial results).
 
 Parallel Reduction instructions, because their Architectural State cannot
 hold the partial results).
 

-*Future specification note: future versions of the REMAP Management instructions
-will extend to EXT1xx Prefixed variants. This will overcome some of the limitations
-present in the 32-bit variants of the REMAP Management instructions that at
-present require direct writing to SVSHAPE0-3 SPRs.  Additional
-REMAP Modes may also be introduced at that time.*
-

 ## Basic principle
 
 The following illustrates why REMAP was added.
 ## Basic principle
 
 The following illustrates why REMAP was added.