add openpower foundation membership link
[libreriscv.git] / openpower.mdwn
1 # Evaluation
2
3 EULA released! looks good.
4
5 Links
6
7 * OpenPOWER Membership
8 <https://openpowerfoundation.org/membership/how-to-join/membership-kit-9-27-16-4/>
9 * OpenPower HDL Mailing list <http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-hdl-cores>
10 * [[openpower/isatables]]
11 * [[openpower/isa]] - pseudo-code extracted from POWER V3.0B PDF spec
12 * [[openpower/gem5]]
13 * [[openpower/pearpc]]
14 * [[openpower/pipeline_operands]] - the allocation of operands on each pipeline
15 * [[3d_gpu/architecture/decoder]]
16 * <https://forums.raptorcs.com/>
17 * <http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-community-dev>
18 * <http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo>
19 * <http://bugs.libre-riscv.org/show_bug.cgi?id=179>
20 * <https://openpowerfoundation.org/?resource_lib=power-isa-version-3-0>
21 * <https://openpowerfoundation.org/?resource_lib=ibm-power-isa-version-2-07-b>
22
23 PowerPC Unit Tests
24
25 * <https://github.com/lioncash/DolphinPPCTests>
26 * <https://github.com/JustinCB/macemu/blob/master/SheepShaver/src/kpx_cpu/src/test/test-powerpc.cpp>
27
28 Summary
29
30 * FP32 is converted to FP64. Requires SimpleV to be active.
31 * FP16 needed
32 * transcendental FP opcodes needed (sin, cos, atan2, root, log1p)
33 * FCVT between 16/32/64 needed
34 * c++11 atomics not very efficient
35 * no 16/48/64 opcodes, needs a shuffle of opcodes. TODO investigate Power VLE
36 * needs escape sequencing (ISAMUX/NS) - see [[openpower/isans_letter]]
37
38 # What we are *NOT* doing:
39
40 * A processor that is fundamentally incompatible (noncompliant) with Power.
41 (**escape-sequencing requires and guarantees compatibility**).
42 * Opcode 4 Signal Processing (SPE)
43 * Opcode 4 Vectors or Opcode 60 VSX (600+ additional instructions)
44 * Avoidable legacy opcodes
45
46 # SimpleV
47
48 see [[simple_v_extension]] - will fit into 48/64/VBLOCK, see below.
49 SimpleV: a "hardware for-loop" which involves type-casting (both) the
50 register files to "a sequence of elements". The **one** instruction
51 (an unmodified **scalar** instruction) is interpreted as a *hardware
52 for-loop* that issues **multiple** internal instructions with
53 sequentially-incrementing register numbers.
54
55 Thus it is completely unnecessary to add any vector opcodes - at all -
56 saving hugely on both hardware and compiler development time when
57 the concept is dropped on top of a pre-existing ISA.
58
59 ## Condition Registers
60
61 Branch Facility (Section 2.3.1 V2.07B and V3.0B) has 4-bit registers: CR0 and CR1. When SimpleV is active, it may be better to set CR6 (the Vector CR field) instead.
62
63 ## Carry
64
65 SimpleV extends (wraps) *scalar* opcodes with a hardware-level for-loop. Therefore, each scalar operation with a carry-in and carry-out will **require its own carry in and out bit**. Therefore, an extra SPR will be required which allows context switches to save this full set of carry bits.
66
67 # Integer Overflow / Saturate
68
69 Typically used on vector operations (audio DSP), it makes no sense to have separate opcodes (Opcode 4 SPE). To be done instead as CSRs / vector-flags on *standard* arithmetic operations.
70
71 # atomics
72
73 Single instruction on RV, and x86, but multiple on Power. Needs investigation, particularly as to why cache flush exists.
74
75 https://www.cl.cam.ac.uk/~pes20/cpp/cpp0xmappings.html
76
77 Hot loops contain significant instruction count, really need new c++11 atomics. To be proposed as new extension because other OpenPower members will need them too
78
79 # FP16
80
81 Doesn't exist in Power, need to work out suitable opcodes, basically means duplicating the entire range of FP32/64 ops, symmetrically.
82
83 Usually done with a fmt field, 2 bit, last one is FP128
84
85 idea: rather than add dozens of new opcodes, add "repurposer" instructions that remap FP32 to 16/32/64/128 and FP64 likewise. can also be done as C instruction, only needs 4 bits to specify.
86
87 # Escape Sequencing
88
89 aka "ISAMUX/NS". Absolutely critical, also to have official endorsement
90 from OpenPower Foundation.
91
92 This will allow extending ISA (see ISAMUX/NS) in a clean fashion
93 (including for and by OpenPower Foundation)
94
95 ## Branches in namespaces
96
97 Branches are fine as it is up to the compiler to decide whether to let the
98 ISAMUX/NS/escape-sequence countdown run out.
99
100 This is all a software / compiler / ABI issue.
101
102 ## Function calls in namespaces
103
104 Storing and restoring the state of the page/subpage CSR should be done by the caller. Or, again, let the countdowns run out.
105
106 If certain alternative configs are expected, they are part of the function ABI which must be spec'd.
107
108 All of this is a software issue (compiler / ABI).
109
110 # Compressed, 48, 64, VBLOCK
111
112 TODO investigate Power VLE (Freescale doc Ref 314-68105)
113
114 Under Esc Seq, move mulli, twi, tdi out of major OP000 then use the
115 entire row, 2 bits instead of 3. greatly simplifies decoder.
116
117 * OP 000-000 and 000-001 for 16 bit compressed, 11 bit instructions
118 * OP 000-010 and 000-011 for 48 bit. 11 bits for SVP P48
119 * OP 000-100 and 000-201 for 64 bit. 11 bits for SVP P64
120 * OP 000-110 and 000-111 for VBLOCK. 11 bits available.
121
122 Note that this requires BE instruction encoding (separate from
123 data BE/LE encoding). BE encoding always places the major opcode in
124 the first 2 bytes of the raw (uninterpreted) sequential instruction
125 byte stream.
126
127 Thus in BE-instruction-mode, the first 2 bytes may be analysed to
128 detect whether the instruction is 16-bit Compressed, 48-bit SVP-P48,
129 64-bit SVP-64, variable-length VBLOCK, or plain 32-bit.
130
131 It is not possible to distinguish LE-encoded 32-bit instructions
132 from LE-encoded 16-bit instructions because in LE-encoded 32-bit
133 instructions, the opcode falls into:
134
135 * bytes 2 and 3 of any given raw (uninterpreted) sequential instruction
136 byte stream for a 32-bit instruction
137 * bytes 0 and 1 for a 16-bit Compressed instruction
138 * bytes 4 and 5 for a 48-bit SVP P48
139 * bytes 6 and 7 for a 64-bit SVP P64
140
141 Clearly this is an impossible situation, therefore BE is the only
142 option. Note: *this is completely separate from BE/LE for data*
143
144 # Compressed 16
145
146 Further "escape-sequencing".
147
148 Only 11 bits available. Idea: have "pages" where one instruction selects
149 the page number. It also specifies for how long that page is activated
150 (terminated on a branch)
151
152 The length to be a maximum of 4 bits, where 0b1111 indicates "permanently active".
153
154 Perhaps split OP000-000 and OP000-001 so that 2 pages can be active.
155
156 Store activation length in a CSR.
157
158 2nd idea: 11 bits can be used for extremely common operations, then length-encoding page selection for further ops, using the full 16 bit range and an entirely new encoding scheme. 1 bit specifies which of 2 pages was selected?
159
160 3rd idea: "stack" mechanism. Allow subpages like a stack, to page in new pages.
161
162 3 bits for subpage number. 4 bits for length, gives 7 bits. 4x7 is 28, then 3 bits can be used to specify "stack depth".
163
164 Requirements are to have one instruction in each subpage which resets all the way back to PowerISA default. The other is a "back up stack by 1".
165
166 # RISCV userspace
167
168 Dual ISA, RV userspace only. Requires PowerISA to be able to context-switch RV registers and CSRs.
169
170 the exception entry point:
171 <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/kernel/exceptions-64s.S?h=v5.4-rc5#n409>
172
173 the rest of the context switch code is in a different file:
174 <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/kernel/entry_64.S?h=v5.4-rc5#n589>