Lines Matching +full:output +full:- +full:only
3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
14 …These APIs may only be provided by certain platforms, and may not be available to all virtual mach…
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
77 …See Section 36.2.1, “Query CCB Command Formats” for the corresponding CCB input and output formats.
79 Only version 0 CCBs are available.
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
106 …See Section 36.2.1, “Query CCB Command Formats” for the corresponding CCB input and output formats.
108 … Version 0 and 1 CCBs are available. Only version 0 CCBs may use Huffman encoded data, whereas only
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
163 [10:8] Output/Destination address type
212 A CCB may only be conditional on exactly one CCB, however, a CCB may be marked both Conditional
213 and Serial to allow execution chaining. The flags do NOT allow fan-out chaining, where multiple CCBs
216 The Pipeline flag is an optimization that directs the output of one CCB (the "source" CCB) directly…
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…
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.
345 36.2.1.1.6. Output Format
347 …Query commands support multiple sizes and encodings for output data streams. There are four possib…
348 …output encodings, and up to four supported element sizes per encoding. Not all output encodings are
349 supported for every command. The format is indicated by a 4-bit field in the CCB:
351 Output Format Code Description
374 …access type used in the CCB command. ADI checking only occurs when reading data. When writing data,
382 …The ADI value is only guaranteed to be checked on the first 64 bytes of each data access. Mismatch…
402 …Converts an input vector in one format to an output vector in another format. All input format typ…
405 …The only supported output format is a padded, byte-aligned output stream, using output codes 0x0 -…
406 …When the specified output element size is larger than the extracted input element size, zeros are …
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
430 uint64_t output;
461 [13:10] Output Format (see Section 36.2.1.1.6, “Output Format”)
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
486 (checking is only guaranteed to be performed when using API
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
517 only enforced if flow control is enabled in Flow Control field.
519 [31:30] Output Data Cache Allocation
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
569 48 8 Output (same fields as Primary Input)
577 … (checking is only guaranteed to be performed when using API
585 … address. (Only available when using version 0 CCBs)
587 … address. (Only available when using version 1 CCBs)
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.
599 …There are two supported formats for the output stream: the bit vector and index array formats (cod…
600 …0xD, and 0xE). For the standard scan command using the bit vector output, for each input element t…
602 …inverted scan command inverts the polarity of the bits in the output. The most significant bit of …
603 …byte of the output stream corresponds to the first element in the input stream. The standard index…
604 …output format contains one array entry for each input element that matched the scan criteria. Each…
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
633 uint64_t output;
660 [13:10] Output Format (see Section 36.2.1.1.6, “Output Format”)
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.
690 48 8 Output (same fields as Primary Input)
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
726 …the input array. The output should therefore contain exactly one bit per index in the input data s…
728 …ead in the bit table, but will always be less than, or equal to, the number of input elements. Only
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…
736 …If the values match, the value from the bit table is used as the output element value. If the valu…
737 match, the output data element value is forced to 0.
740 …ditional processing based on any additional non-index bits remains unchanged, and still forces the…
744 …There are two supported formats for the output stream: the bit vector and index array formats (cod…
746 output format was a bit array.
748 …The return value of the CCB completion area contains the number of bits set in the output bit vect…
749 …or number of elements in the output index array. The “number of elements processed” field in the C…
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
766 uint64_t output;
797 [13:10] Output Format (see Section 36.2.1.1.6, “Output Format”)
808 48 8 Output (same fields as Primary Input)
816 (checking is only guaranteed to be performed when using API
820 CCB header. Address must be 64-byte aligned (CCB version
821 0) or 16-byte aligned (CCB version 1).
835 …which input elements to include in the output. For each bit set at a given index N within the bit …
836 …the Nth input element is included in the output. If the bit is not set, the element is not include…
840 …The only supported output format is a padded, byte-aligned output stream. The stream follows the s…
841 … rules and restrictions as padded output stream described in Section 36.2.1.2, “Extract command”.
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
861 uint64_t output;
892 … [13:10] Output Format (see Section 36.2.1.1.6, “Output Format”)
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
903 48 8 Output (same fields as Primary Input)
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
913 command CCB will only execute when all previous commands submitted in the same request have
914 …completed. This is stronger than the conditional flag sequencing, which is only dependent on a sin…
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
1015 8 4 Number of bytes of output produced
1024 The CCB completion area should be treated as read-only by guest software. The CCB execution status
1027 byte becomes non-zero.
1035 A buffer overflow indicates that the results of the operation exceeded the size of the output buffe…
1036 in the CCB. The operation can be retried by resubmitting the CCB with a larger output buffer.
1039 triggered if the CCB output is directed at a non-existent secondary input and the pipelining hint i…
1051 …In the case of pipelined CCBs, a page overflow error will be triggered if the output from the pipe…
1057 …Command timeout indicates that the CCB execution began, but did not complete within a pre-determin…
1058 … limit set by the virtual machine. The command may have produced some or no output. The CCB may be
1071 …The output size field indicates the number of bytes of valid output in the destination buffer. Thi…
1075 …machine queue. The time units are fixed, but unspecified, allowing only relative timing comparisons
1082 …The return value and extended return value fields are output locations for commands which do not u…
1083 …a destination output buffer, or have secondary return results. The field is not valid for all poss…
1139 [7] All-or-nothing flag
1163 … to load data. ADI checking will still be done when loading real-addressed memory. This bit is only
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:
1204 …The API has a reserved input and output register which will be used in subsequent minor versions o…
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
1253 restricted operation availability may apply only to the first unsuccessfully
1303 by the 64-byte aligned real address of the CCBs completion area.
1329 …The position return value is only valid when the state is ENQUEUED. The value returned is the numb…
1332 … The dax return value is only valid when the state is ENQUEUED. The value returned is the DAX unit
1336 … The queue return value is only valid when the state is ENQUEUED. The value returned is the DAX
1343 EBADALIGN address is not on a 64-byte aligned.
1360 the 64-byte aligned real address of the CCBs completion area.
1400 meaningful output on which the target CCB could operate.
1405 EBADALIGN address is not on a 64-byte aligned.