Lines Matching +full:processor +full:- +full:b +full:- +full:side
3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
16 live-migration and other system management activities.
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
81 36.1.1.2. "ORCL,sun4v-dax-fc" Device Compatibility
82 … "ORCL,sun4v-dax-fc" is compatible with the "ORCL,sun4v-dax" interface, and includes additional CCB
85 36.1.1.3. "ORCL,sun4v-dax2" Device Compatibility
88 • No-op/Sync
114 …guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device node”). If the de…
115 …node indicates N interrupts available, the guest may use any value from 0 to N - 1 (inclusive) in …
136 All CCBs begin with a common 32-bit header.
148 0x00 No Operation (No-op) or Sync
159 0b'00 No address
160 0b'01 Alternate context virtual address
161 0b'10 Real address
162 0b'11 Primary context virtual address
164 0b'000 No address
165 0b'001 Alternate context virtual address
166 0b'010 Real address
167 0b'011 Primary context virtual address
168 0b'100 Reserved
169 0b'101 Reserved
170 0b'110 Reserved
171 0b'111 Reserved
180 0b'000 No address
181 0b'001 Alternate context virtual address
182 0b'010 Real address
183 0b'011 Primary context virtual address
184 0b'100 Reserved
185 0b'101 Reserved
186 0b'110 Reserved
187 0b'111 Reserved
189 0b'000 No address
190 0b'001 Alternate context virtual address
191 0b'010 Real address
192 0b'011 Primary context virtual address
193 0b'100 Reserved
194 0b'101 Reserved
195 0b'110 Reserved
196 0b'111 Reserved
198 0b'00 No address
199 0b'01 Alternate context virtual address
200 0b'10 Real address
201 0b'11 Primary context virtual address
213 and Serial to allow execution chaining. The flags do NOT allow fan-out chaining, where multiple CCBs
238 …for the submitting virtual processor. Virtual addresses which cannot be translated by the virtual …
248 encoded data) and secondary data streams (meta-data for the encoded data).
252 …The primary input format code is a 4-bit field when it is used. There are 10 primary input formats…
310 …always encoded in a fixed width, bit-packed format. The bits are read from most significant bit to…
333 …Bit-wise input data streams may have any alignment within the base addressed byte. The offset, spe…
338 This field should be zero for any byte-wise primary input data streams.
349 supported for every command. The format is indicated by a 4-bit field in the CCB:
405 …The only supported output format is a padded, byte-aligned output stream, using output codes 0x0 -…
408 …padded to the most significant bit side till the next byte boundary. Next, if the output element s…
410 …CCB. If the output element size is smaller than the byte-padded input element size, the input elem…
411 …truncated by dropped from the least significant byte side until the selected output size is reache…
416 The extract CCB is a 64-byte “short format” CCB.
418 …he extract CCB command format can be specified by the following packed C structure for a big-endian
463 to be added to the left side of output elements. A value of 0
464 causes padding bytes to be added to the right side of output
495 0b'00 Disable flow control
496 0b'01 Enable flow control (only valid with "ORCL,sun4v-
497 dax-fc" compatible virtual device variants)
498 0b'10 Reserved
499 0b'11 Reserved
511 0b'00 Connect to primary input
512 0b'01 Connect to secondary input
513 0b'10 Reserved
514 0b'11 Reserved
521 0b'00 Do not allocate cache lines for output data stream.
522 0b'01 Force cache lines for output data stream to be
525 0b'10 Allocate cache lines for output data stream, but allow
530 0b'11 Reserved
534 0b'00 Number of primary symbols
535 0b'01 Number of primary bytes
536 0b'10 Number of primary bits
537 0b'11 Reserved
596 …range commands, the boundary conditions can be specified as greater-than-or-equal-to a value, less-
597 than-or-equal-to a value, or both by using two boundary values.
619 These commands are 128-byte “long format” CCBs.
621 The scan CCB command format can be specified by the following packed C structure for a big-endian
673 operand, minus 1. Values 0xF-0x1E are reserved. A value of
679 operand, minus 1. Values 0xF-0x1E are reserved. A value of
687 than 4 bytes, the value is left-aligned to the lowest address bytes.
689 is less than 4 bytes, the value is left-aligned to the lowest address bytes.
695 is less than 8 bytes, the valid bytes are left-aligned to the lowest address.
698 operand is less than 8 bytes, the valid bytes are left-aligned to the lowest
702 is less than 12 bytes, the valid bytes are left-aligned to the lowest address.
705 operand is less than 12 bytes, the valid bytes are left-aligned to the lowest
709 is less than 16 bytes, the valid bytes are left-aligned to the lowest address.
712 operand is less than 16 bytes, the valid bytes are left-aligned to the lowest
734 …used as an index into the bit table. The most significant 9 bits (when using 3-byte input elements…
735 …bit (when using 2-byte input elements) are compared against a fixed 9-bit test value provided in t…
740 …additional processing based on any additional non-index bits remains unchanged, and still forces t…
752 These commands are 64-byte “short format” CCBs.
754 … translate CCB command format can be specified by the following packed C structure for a big-endian
820 CCB header. Address must be 64-byte aligned (CCB version
821 0) or 16-byte aligned (CCB version 1).
840 …The only supported output format is a padded, byte-aligned output stream. The stream follows the s…
847 The select CCB is a 64-byte “short format” CCB.
849 …The select CCB command format can be specified by the following packed C structure for a big-endian
894 … to be added to the left side of output elements. A value of 0
895 … causes padding bytes to be added to the right side of output
907 36.2.1.6. No-op and Sync commands
908 … The no-op (no operation) command is a CCB which has no processing effect. The CCB, when processed
910 the serial-conditional flags set in order to restrict when it executes.
912 … The sync command is a variant of the no-op command which with restricted execution timing. A sync
922 These commands are 64-byte “short format” CCBs.
924 … The no-op CCB command format can be specified by the following packed C structure for a big-endian
950 CCB functions as a No-op command.
956 All CCB commands use a common 128-byte Completion Area format, which can be specified by the
957 following packed C structure for a big-endian machine:
976 … The Completion Area must be a 128-byte aligned memory location. The exact layout can be described
988 0x5-0xF Reserved
1001 0x4-0x6 Reserved
1006 0xB-0xD Reserved
1009 0x10-0x7F Reserved
1011 0x81-0xFF Reserved
1024 The CCB completion area should be treated as read-only by guest software. The CCB execution status
1027 byte becomes non-zero.
1029 CCBs which complete with status 0x2 or 0x3 may produce partial results and/or side effects due to p…
1039 triggered if the CCB output is directed at a non-existent secondary input and the pipelining hint i…
1057 …Command timeout indicates that the CCB execution began, but did not complete within a pre-determin…
1133 0b'00 CCBs requesting alternate context are rejected
1134 0b'01 Reserved
1135 0b'10 CCBs requesting alternate context use secondary context
1136 0b'11 CCBs requesting alternate context use nucleus context
1139 [7] All-or-nothing flag
1142 0b'00 Real address
1143 0b'01 Virtual address in primary context
1144 0b'10 Virtual address in secondary context
1145 0b'11 Virtual address in nucleus context
1148 0b'00 Reserved
1149 0b'01 Reserved
1150 0b'10 Query command
1151 0b'11 Reserved
1163 …address to load data. ADI checking will still be done when loading real-addressed memory. This bit…
1176 …The all-or-nothing flag specifies whether the virtual machine should allow partial submissions of …
1177 … input CCB array. When using CCBs with serial-conditional flags, it is strongly recommended to use
1178 …the all-or-nothing flag to avoid broken conditional chains. Using long CCB chains on a machine und…
1180 …When submitting serial-conditional CCBs without the all-or-nothing flag, guest software must manua…
1181 …implement the serial-conditional behavior at any point where the chain was not submitted in a sing…
1185 …When the all-or-nothing flag is not specified, callers should check the value of length in ret1 to…
1194 length value in ret1 will be a multi-field value defined as follows:
1224 EBADALIGN CCB array is not on a 64-byte boundary, or the array length is not a multiple
1243 ETOOMANY The request was submitted with the all-or-nothing flag set, and the array size is
1303 by the 64-byte aligned real address of the CCBs completion area.
1343 EBADALIGN address is not on a 64-byte aligned.
1360 the 64-byte aligned real address of the CCBs completion area.
1405 EBADALIGN address is not on a 64-byte aligned.