Lines Matching +full:64 +full:- +full:byte
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 …
123 …CCBs are either 64 or 128 bytes long, depending on the operation type. The exact contents of the C…
136 All CCBs begin with a common 32-bit header.
148 0x00 No Operation (No-op) or Sync
203 The Long CCB flag indicates whether the submitted CCB is 64 or 128 bytes long; value is 0 for 64 by…
213 and Serial to allow execution chaining. The flags do NOT allow fan-out chaining, where multiple CCBs
231 …The input of the target CCB must start within 64 bytes of the output of the source CCB or the pipe…
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…
256 0x0 Fixed width byte packed Up to 16 bytes
259 within a byte
260 …0x2 Variable width byte packed Data stream of lengths must be provided as a secon…
262 … 0x4 Fixed width byte packed with run Up to 16 bytes; data stream of run lengths must be
266 … within a byte; data stream of run lengths must be provided
268 … 0x8 Fixed width byte packed with Up to 16 bytes before the encoding; compressed stream
270 … OZIP (CCB version 1) encoding within a byte; pointer to the encoding table must be
274 … OZIP (CCB version 1) encoding least significant bit within a byte; pointer to the encoding
276 … 0xA Variable width byte packed with Up to 16 bytes before the encoding; compressed stream
278 … OZIP (CCB version 1) encoding within a byte; data stream of lengths must be provided as
288 …0xC Fixed width byte packed with Up to 16 bytes before the encoding; compressed str…
290 … Huffman (CCB version 0) or within a byte; data stream of run lengths must be provided
295 … Huffman (CCB version 0) or significant bit to least significant bit within a byte; data
310 …always encoded in a fixed width, bit-packed format. The bits are read from most significant bit to…
311 …significant bit within a byte. There are two encoding options for the secondary input stream data …
333 …Bit-wise input data streams may have any alignment within the base addressed byte. The offset, spe…
335 … indicates that the first input element begins at the most significant bit in the first byte, and a
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:
352 0x0 Byte aligned, 1 byte elements
353 0x1 Byte aligned, 2 byte elements
354 0x2 Byte aligned, 4 byte elements
355 0x3 Byte aligned, 8 byte elements
356 0x4 16 byte aligned, 16 byte elements
365 0xD 2 byte elements where each element is the index value of a bit,
367 0xE 4 byte elements where each element is the index value of a bit,
382 …The ADI value is only guaranteed to be checked on the first 64 bytes of each data access. Mismatch…
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…
409 …than the byte padded input element, bytes of value 0 are added based on the Padding Direction bit …
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
496 0b'01 Enable flow control (only valid with "ORCL,sun4v-
497 dax-fc" compatible virtual device variants)
515 [59:40] Output buffer size given in units of 64 bytes, minus 1. Value of
516 0 means 64 bytes, value of 1 means 128 bytes, etc. Buffer size is
584 … 0 Huffman encoding. Must use 64 byte aligned table
586 … 1 OZIP encoding. Must use 16 byte aligned table
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.
603 …byte of the output stream corresponds to the first element in the input stream. The standard index…
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.
693 64 4 Next 4 most significant bytes of first scan criteria operand occurring after the
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
701 bytes specified at offset 64, if needed by the operand size. If first operand
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
733 …additional processing of the output values. If 2 or 3 byte values are used, the least significant …
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
800 in the input values, when using 2 or 3 byte input elements.
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
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
977 using byte offsets and sizes relative to the memory base:
988 0x5-0xF Reserved
1001 0x4-0x6 Reserved
1006 0xB-0xD Reserved
1009 0x10-0x7F Reserved
1011 0x81-0xFF Reserved
1022 64 64 Extended return value
1024 The CCB completion area should be treated as read-only by guest software. The CCB execution status
1025 byte will be cleared by the Hypervisor to reflect the pending execution status when the CCB is subm…
1027 byte becomes non-zero.
1032 completes with a status byte of 0x2, the error reason code byte can be read to determine what corre…
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…
1110 length must be a multiple of 64 bytes. If length is zero, the maximum supported array length will be
1139 [7] All-or-nothing flag
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
1225 of 64 bytes.
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.