Lines Matching +full:address +full:- +full:address +full:- +full:data
3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
13 …The following APIs provide access via the Hypervisor to hardware assisted data processing function…
16 live-migration and other system management activities.
18 36.1. Data Analytics Accelerator
19 …The Data Analytics Accelerator (DAX) functionality is a collection of hardware coprocessors that p…
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
21 …the following data query operations: search, extraction, compression, decompression, and translati…
24 …The DAX is a virtual device to sun4v guests, with supported data operations indicated by the virtu…
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
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 …
124 …are command specific, but all CCBs contain at least one memory buffer address. All memory locations
132 via the ccb_kill API call. Changes in virtual address mappings occurring after CCB submission are n…
133 guaranteed to be visible, and as such all virtual address updates need to be synchronized with CCB
136 All CCBs begin with a common 32-bit header.
148 0x00 No Operation (No-op) or Sync
158 [12:11] Table address type
159 0b'00 No address
160 0b'01 Alternate context virtual address
161 0b'10 Real address
162 0b'11 Primary context virtual address
163 [10:8] Output/Destination address type
164 0b'000 No address
165 0b'001 Alternate context virtual address
166 0b'010 Real address
167 0b'011 Primary context virtual address
172 [7:5] Secondary source address type
180 0b'000 No address
181 0b'001 Alternate context virtual address
182 0b'010 Real address
183 0b'011 Primary context virtual address
188 [4:2] Primary source address type
189 0b'000 No address
190 0b'001 Alternate context virtual address
191 0b'010 Real address
192 0b'011 Primary context virtual address
197 [1:0] Completion area address type
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
234 … The various address type fields indicate how the various address values used in the CCB should be
236 …ich are not applicable to the given CCB command should be indicated as type 0 (No address). Virtual
239 …will result in the CCB submission being rejected, with the causal virtual address indicated. The C…
240 …may be resubmitted after inserting the translation, or the address may be translated by guest soft…
241 resubmitted using the real address translation.
244 36.2.1.1. Supported Data Formats, Elements Sizes and Offsets
245 … Data for query commands may be encoded in multiple possible formats. The data query commands use a
246 …common set of values to indicate the encoding formats of the data being processed. Some encoding f…
247 …require multiple data streams for processing, requiring the specification of both primary data for…
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…
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
278 … OZIP (CCB version 1) encoding within a byte; data stream of lengths must be provided as
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
303 …For primary input data streams with fixed size elements, the element size must be indicated in the…
309 …For primary input data streams which require a secondary input stream, the secondary input stream …
310 …always encoded in a fixed width, bit-packed format. The bits are read from most significant bit to…
311 …ant bit within a byte. There are two encoding options for the secondary input stream data elements,
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.
347 …Query commands support multiple sizes and encodings for output data streams. There are four possib…
349 supported for every command. The format is indicated by a 4-bit field in the CCB:
371 36.2.1.1.7. Application Data Integrity (ADI)
374 …access type used in the CCB command. ADI checking only occurs when reading data. When writing data,
377 …An ADI version value of 0 or 0xF indicates the ADI checking is disabled for that data access, even…
379 …also an option to disable ADI checking for all inputs accessed via virtual address for all CCBs su…
382 …The ADI value is only guaranteed to be checked on the first 64 bytes of each data access. Mismatch…
383 …subsequent data chunks may not be detected, so guest software should be careful to use page size c…
388 … All data accesses used in CCB commands must be bounded within a single memory page. When addresses
389 …are provided using a virtual address, the page size for checking is extracted from the TTE for tha…
390 …address. When using real addresses, the guest must supply the page size in the same field as the a…
405 …The only supported output format is a padded, byte-aligned output stream, using output codes 0x0 -…
410 …CCB. If the output element size is smaller than the byte-padded input element size, the input elem…
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
469 [63:60] ADI version (see Section 36.2.1.1.7, “Application Data
475 [58:6] Completion area address bits [58:6]. Address type is
481 [63:60] ADI version (see Section 36.2.1.1.7, “Application Data
483 [59:56] If using real address, these bits should be filled in with the
485 the virtual machine to use when accessing this data stream
487 version 1.1 and later). If using a virtual address, this field will
488 be used as as primary input address bits [59:56].
489 [55:0] Primary input address bits [55:0]. Address type is determined
491 24 8 Data Access Control
496 0b'01 Enable flow control (only valid with "ORCL,sun4v-
497 dax-fc" compatible virtual device variants)
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
526 existing cache lines associated with the data to remain
572 … [63:60] ADI version (see Section 36.2.1.1.7, “Application Data
574 … [59:56] If using real address, these bits should be filled in with the
576 … the virtual machine to use when accessing this data stream
578 … version 1.1 and later). If using a virtual address, this field will
579 … be used as as symbol table address bits [59:56].
580 … [55:4] Symbol table address bits [55:4]. Address type is determined
585 … address. (Only available when using version 0 CCBs)
587 … address. (Only available when using version 1 CCBs)
592 …The scan commands search a stream of input data elements for values which match the selection crit…
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
683 24 8 Data Access Control (same fields as Section 36.2.1.2, “Extract command”)
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
699 address.
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
706 address.
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
713 address.
726 …nput array. The output should therefore contain exactly one bit per index in the input data stream,
730 … encoded input streams are allowed. The primary input data element size must be 3 bytes or less.
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…
737 match, the output data element value is forced to 0.
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
803 24 8 Data Access Control (same fields as Section 36.2.1.2, “Extract command”,
811 [63:60] ADI version (see Section 36.2.1.1.7, “Application Data
813 [59:56] If using real address, these bits should be filled in with the
815 the virtual machine to use when accessing this data stream
817 version 1.1 and later). If using a virtual address, this field will
818 be used as as bit table address bits [59:56]
819 [55:4] Bit table address bits [55:4]. Address type is determined by
820 CCB header. Address must be 64-byte aligned (CCB version
821 0) or 16-byte aligned (CCB version 1).
834 …The select command filters the primary input data stream by using a secondary input bit vector to …
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
900 …24 8 Data Access Control (same fields as Section 36.2.1.2, “Extract comm…
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
1005 0xA Data format error
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.
1030 execution of the CCB command. Some valid data may be accessible depending on the fault type, howeve…
1039 triggered if the CCB output is directed at a non-existent secondary input and the pipelining hint i…
1042 size associated with a given address. No data will have been read or written past the page boundary…
1057 …Command timeout indicates that the CCB execution began, but did not complete within a pre-determin…
1065 …A data format error indicates that the input data stream did not follow the specified data input f…
1079 …Some data query commands process data in units of elements. If applicable to the command, the numb…
1090 arg0 address
1096 ret2 status data
1100 … machine. The CCBs are passed in a linear array indicated by address. length indicates the size of
1108 The address should be aligned to the size indicated by length, rounded up to the nearest power of
1115 Virtual machines should never reject submissions based on the alignment of address if the
1119 A guest may choose to submit addresses used in this API function, including the CCB array address,
1120 as either a real or virtual addresses, with the type of each address indicated in flags. Virtual ad…
1139 [7] All-or-nothing flag
1140 [6] If address is a virtual address, treat its translation context as privileged
1141 [5:4] Address type of address:
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
1159 … The CCB submission type and address type for the CCB array must be provided in the flags argument.
1163 …address to load data. ADI checking will still be done when loading real-addressed memory. This bit…
1165 …more information about using ADI and DAX, see Section 36.2.1.1.7, “Application Data Integrity (ADI…
1167 …By default, all virtual addresses are treated as user addresses. If the virtual address translatio…
1172 …active at the time of the submission. The address type field within a CCB allows each address to r…
1173 …translation in an alternate address context. The address context used when the alternate address c…
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:
1201 …The value of status data depends on the status value. See error status code descriptions for detai…
1202 …The value is undefined for status values that do not specifically list a value for the status data.
1224 EBADALIGN CCB array is not on a 64-byte boundary, or the array length is not a multiple
1226 ENORADDR A real address used either for the CCB array, or within one of the submitted
1229 ENOMAP A virtual address used either for the CCB array, or within one of the submitted
1232 mapping, or by converting the virtual address into a real address. Due to the
1233 shared nature of address translation resources, there is no theoretical limit on
1235 implement some real address based backup. The virtual address which failed
1236 translation is returned as status data in ret2. Some CCBs may have been
1243 ETOOMANY The request was submitted with the all-or-nothing flag set, and the array size is
1247 ENOACCESS The guest does not have permission to submit CCBs, or an address used in a
1249 permission on the destination buffer address, for example). A virtual address
1250 which fails permission checking is returned as status data in ret2. Some
1257 data provides additional information about scope of the restricted availability
1295 arg0 address
1303 by the 64-byte aligned real address of the CCBs completion area.
1343 EBADALIGN address is not on a 64-byte aligned.
1344 ENORADDR The real address provided for address is not valid.
1355 arg0 address
1360 the 64-byte aligned real address of the CCBs completion area.
1405 EBADALIGN address is not on a 64-byte aligned.
1406 ENORADDR The real address provided for address is not valid.