1434 lines · plain
1Excerpt from UltraSPARC Virtual Machine Specification2Compiled from version 3.0.20+153Publication date 2017-09-25 08:214Copyright © 2008, 2015 Oracle and/or its affiliates. All rights reserved.5Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"6Authors:7 Charles Kunzman8 Sam Glidden9 Mark Cianchetti10 11 12Chapter 36. Coprocessor services13 The following APIs provide access via the Hypervisor to hardware assisted data processing functionality.14 These APIs may only be provided by certain platforms, and may not be available to all virtual machines15 even on supported platforms. Restrictions on the use of these APIs may be imposed in order to support16 live-migration and other system management activities.17 1836.1. Data Analytics Accelerator19 The Data Analytics Accelerator (DAX) functionality is a collection of hardware coprocessors that provide20 high speed processoring of database-centric operations. The coprocessors may support one or more of21 the following data query operations: search, extraction, compression, decompression, and translation. The22 functionality offered may vary by virtual machine implementation.23 24 The DAX is a virtual device to sun4v guests, with supported data operations indicated by the virtual device25 compatibility property. Functionality is accessed through the submission of Command Control Blocks26 (CCBs) via the ccb_submit API function. The operations are processed asynchronously, with the status27 of the submitted operations reported through a Completion Area linked to each CCB. Each CCB has a28 separate Completion Area and, unless execution order is specifically restricted through the use of serial-29 conditional flags, the execution order of submitted CCBs is arbitrary. Likewise, the time to completion30 for a given CCB is never guaranteed.31 32 Guest software may implement a software timeout on CCB operations, and if the timeout is exceeded, the33 operation may be cancelled or killed via the ccb_kill API function. It is recommended for guest software34 to implement a software timeout to account for certain RAS errors which may result in lost CCBs. It is35 recommended such implementation use the ccb_info API function to check the status of a CCB prior to36 killing it in order to determine if the CCB is still in queue, or may have been lost due to a RAS error.37 38 There is no fixed limit on the number of outstanding CCBs guest software may have queued in the virtual39 machine, however, internal resource limitations within the virtual machine can cause CCB submissions40 to be temporarily rejected with EWOULDBLOCK. In such cases, guests should continue to attempt41 submissions until they succeed; waiting for an outstanding CCB to complete is not necessary, and would42 not be a guarantee that a future submission would succeed.43 44 The availability of DAX coprocessor command service is indicated by the presence of the DAX virtual45 device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device46 node”).47 4836.1.1. DAX Compatibility Property49 The query functionality may vary based on the compatibility property of the virtual device:50 5136.1.1.1. "ORCL,sun4v-dax" Device Compatibility52 Available CCB commands:53 54 • No-op/Sync55 56 • Extract57 58 • Scan Value59 60 • Inverted Scan Value61 62 • Scan Range63 64 65 50966 Coprocessor services67 68 69 • Inverted Scan Range70 71 • Translate72 73 • Inverted Translate74 75 • Select76 77 See Section 36.2.1, “Query CCB Command Formats” for the corresponding CCB input and output formats.78 79 Only version 0 CCBs are available.80 8136.1.1.2. "ORCL,sun4v-dax-fc" Device Compatibility82 "ORCL,sun4v-dax-fc" is compatible with the "ORCL,sun4v-dax" interface, and includes additional CCB83 bit fields and controls.84 8536.1.1.3. "ORCL,sun4v-dax2" Device Compatibility86 Available CCB commands:87 88 • No-op/Sync89 90 • Extract91 92 • Scan Value93 94 • Inverted Scan Value95 96 • Scan Range97 98 • Inverted Scan Range99 100 • Translate101 102 • Inverted Translate103 104 • Select105 106 See Section 36.2.1, “Query CCB Command Formats” for the corresponding CCB input and output formats.107 108 Version 0 and 1 CCBs are available. Only version 0 CCBs may use Huffman encoded data, whereas only109 version 1 CCBs may use OZIP.110 11136.1.2. DAX Virtual Device Interrupts112 The DAX virtual device has multiple interrupts associated with it which may be used by the guest if113 desired. The number of device interrupts available to the guest is indicated in the virtual device node of the114 guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device node”). If the device115 node indicates N interrupts available, the guest may use any value from 0 to N - 1 (inclusive) in a CCB116 interrupt number field. Using values outside this range will result in the CCB being rejected for an invalid117 field value.118 119 The interrupts may be bound and managed using the standard sun4v device interrupts API (Chapter 16,120 Device interrupt services). Sysino interrupts are not available for DAX devices.121 12236.2. Coprocessor Control Block (CCB)123 CCBs are either 64 or 128 bytes long, depending on the operation type. The exact contents of the CCB124 are command specific, but all CCBs contain at least one memory buffer address. All memory locations125 126 127 510128 Coprocessor services129 130 131referenced by a CCB must be pinned in memory until the CCB either completes execution or is killed132via the ccb_kill API call. Changes in virtual address mappings occurring after CCB submission are not133guaranteed to be visible, and as such all virtual address updates need to be synchronized with CCB134execution.135 136All CCBs begin with a common 32-bit header.137 138Table 36.1. CCB Header Format139Bits Field Description140[31:28] CCB version. For API version 2.0: set to 1 if CCB uses OZIP encoding; set to 0 if the CCB141 uses Huffman encoding; otherwise either 0 or 1. For API version 1.0: always set to 0.142[27] When API version 2.0 is negotiated, this is the Pipeline Flag [512]. It is reserved in143 API version 1.0144[26] Long CCB flag [512]145[25] Conditional synchronization flag [512]146[24] Serial synchronization flag147[23:16] CCB operation code:148 0x00 No Operation (No-op) or Sync149 0x01 Extract150 0x02 Scan Value151 0x12 Inverted Scan Value152 0x03 Scan Range153 0x13 Inverted Scan Range154 0x04 Translate155 0x14 Inverted Translate156 0x05 Select157[15:13] Reserved158[12:11] Table address type159 0b'00 No address160 0b'01 Alternate context virtual address161 0b'10 Real address162 0b'11 Primary context virtual address163[10:8] Output/Destination address type164 0b'000 No address165 0b'001 Alternate context virtual address166 0b'010 Real address167 0b'011 Primary context virtual address168 0b'100 Reserved169 0b'101 Reserved170 0b'110 Reserved171 0b'111 Reserved172[7:5] Secondary source address type173 174 175 511176 Coprocessor services177 178 179Bits Field Description180 0b'000 No address181 0b'001 Alternate context virtual address182 0b'010 Real address183 0b'011 Primary context virtual address184 0b'100 Reserved185 0b'101 Reserved186 0b'110 Reserved187 0b'111 Reserved188[4:2] Primary source address type189 0b'000 No address190 0b'001 Alternate context virtual address191 0b'010 Real address192 0b'011 Primary context virtual address193 0b'100 Reserved194 0b'101 Reserved195 0b'110 Reserved196 0b'111 Reserved197[1:0] Completion area address type198 0b'00 No address199 0b'01 Alternate context virtual address200 0b'10 Real address201 0b'11 Primary context virtual address202 203The Long CCB flag indicates whether the submitted CCB is 64 or 128 bytes long; value is 0 for 64 bytes204and 1 for 128 bytes.205 206The Serial and Conditional flags allow simple relative ordering between CCBs. Any CCB with the Serial207flag set will execute sequentially relative to any previous CCB that is also marked as Serial in the same208CCB submission. CCBs without the Serial flag set execute independently, even if they are between CCBs209with the Serial flag set. CCBs marked solely with the Serial flag will execute upon the completion of the210previous Serial CCB, regardless of the completion status of that CCB. The Conditional flag allows CCBs211to conditionally execute based on the successful execution of the closest CCB marked with the Serial flag.212A CCB may only be conditional on exactly one CCB, however, a CCB may be marked both Conditional213and Serial to allow execution chaining. The flags do NOT allow fan-out chaining, where multiple CCBs214execute in parallel based on the completion of another CCB.215 216The Pipeline flag is an optimization that directs the output of one CCB (the "source" CCB) directly to217the input of the next CCB (the "target" CCB). The target CCB thus does not need to read the input from218memory. The Pipeline flag is advisory and may be dropped.219 220Both the Pipeline and Serial bits must be set in the source CCB. The Conditional bit must be set in the221target CCB. Exactly one CCB must be made conditional on the source CCB; either 0 or 2 target CCBs222is invalid. However, Pipelines can be extended beyond two CCBs: the sequence would start with a CCB223with both the Pipeline and Serial bits set, proceed through CCBs with the Pipeline, Serial, and Conditional224bits set, and terminate at a CCB that has the Conditional bit set, but not the Pipeline bit.225 226 227 512228 Coprocessor services229 230 231 The input of the target CCB must start within 64 bytes of the output of the source CCB or the pipeline flag232 will be ignored. All CCBs in a pipeline must be submitted in the same call to ccb_submit.233 234 The various address type fields indicate how the various address values used in the CCB should be235 interpreted by the virtual machine. Not all of the types specified are used by every CCB format. Types236 which are not applicable to the given CCB command should be indicated as type 0 (No address). Virtual237 addresses used in the CCB must have translation entries present in either the TLB or a configured TSB238 for the submitting virtual processor. Virtual addresses which cannot be translated by the virtual machine239 will result in the CCB submission being rejected, with the causal virtual address indicated. The CCB240 may be resubmitted after inserting the translation, or the address may be translated by guest software and241 resubmitted using the real address translation.242 24336.2.1. Query CCB Command Formats24436.2.1.1. Supported Data Formats, Elements Sizes and Offsets245 Data for query commands may be encoded in multiple possible formats. The data query commands use a246 common set of values to indicate the encoding formats of the data being processed. Some encoding formats247 require multiple data streams for processing, requiring the specification of both primary data formats (the248 encoded data) and secondary data streams (meta-data for the encoded data).249 25036.2.1.1.1. Primary Input Format251 252 The primary input format code is a 4-bit field when it is used. There are 10 primary input formats available.253 The packed formats are not endian neutral. Code values not listed below are reserved.254 255 Code Format Description256 0x0 Fixed width byte packed Up to 16 bytes257 0x1 Fixed width bit packed Up to 15 bits (CCB version 0) or 23 bits (CCB version258 1); bits are read most significant bit to least significant bit259 within a byte260 0x2 Variable width byte packed Data stream of lengths must be provided as a secondary261 input262 0x4 Fixed width byte packed with run Up to 16 bytes; data stream of run lengths must be263 length encoding provided as a secondary input264 0x5 Fixed width bit packed with run Up to 15 bits (CCB version 0) or 23 bits (CCB version265 length encoding 1); bits are read most significant bit to least significant bit266 within a byte; data stream of run lengths must be provided267 as a secondary input268 0x8 Fixed width byte packed with Up to 16 bytes before the encoding; compressed stream269 Huffman (CCB version 0) or bits are read most significant bit to least significant bit270 OZIP (CCB version 1) encoding within a byte; pointer to the encoding table must be271 provided272 0x9 Fixed width bit packed with Up to 15 bits (CCB version 0) or 23 bits (CCB version273 Huffman (CCB version 0) or 1); compressed stream bits are read most significant bit to274 OZIP (CCB version 1) encoding least significant bit within a byte; pointer to the encoding275 table must be provided276 0xA Variable width byte packed with Up to 16 bytes before the encoding; compressed stream277 Huffman (CCB version 0) or bits are read most significant bit to least significant bit278 OZIP (CCB version 1) encoding within a byte; data stream of lengths must be provided as279 a secondary input; pointer to the encoding table must be280 provided281 282 283 513284 Coprocessor services285 286 287 Code Format Description288 0xC Fixed width byte packed with Up to 16 bytes before the encoding; compressed stream289 run length encoding, followed by bits are read most significant bit to least significant bit290 Huffman (CCB version 0) or within a byte; data stream of run lengths must be provided291 OZIP (CCB version 1) encoding as a secondary input; pointer to the encoding table must292 be provided293 0xD Fixed width bit packed with Up to 15 bits (CCB version 0) or 23 bits(CCB version 1)294 run length encoding, followed by before the encoding; compressed stream bits are read most295 Huffman (CCB version 0) or significant bit to least significant bit within a byte; data296 OZIP (CCB version 1) encoding stream of run lengths must be provided as a secondary297 input; pointer to the encoding table must be provided298 299 If OZIP encoding is used, there must be no reserved bytes in the table.300 30136.2.1.1.2. Primary Input Element Size302 303 For primary input data streams with fixed size elements, the element size must be indicated in the CCB304 command. The size is encoded as the number of bits or bytes, minus one. The valid value range for this305 field depends on the input format selected, as listed in the table above.306 30736.2.1.1.3. Secondary Input Format308 309 For primary input data streams which require a secondary input stream, the secondary input stream is310 always encoded in a fixed width, bit-packed format. The bits are read from most significant bit to least311 significant bit within a byte. There are two encoding options for the secondary input stream data elements,312 depending on whether the value of 0 is needed:313 314 Secondary Input Description315 Format Code316 0 Element is stored as value minus 1 (0 evaluates to 1, 1 evaluates317 to 2, etc)318 1 Element is stored as value319 32036.2.1.1.4. Secondary Input Element Size321 322 Secondary input element size is encoded as a two bit field:323 324 Secondary Input Size Description325 Code326 0x0 1 bit327 0x1 2 bits328 0x2 4 bits329 0x3 8 bits330 33136.2.1.1.5. Input Element Offsets332 333 Bit-wise input data streams may have any alignment within the base addressed byte. The offset, specified334 from most significant bit to least significant bit, is provided as a fixed 3 bit field for each input type. A335 value of 0 indicates that the first input element begins at the most significant bit in the first byte, and a336 value of 7 indicates it begins with the least significant bit.337 338 This field should be zero for any byte-wise primary input data streams.339 340 341 514342 Coprocessor services343 344 34536.2.1.1.6. Output Format346 347 Query commands support multiple sizes and encodings for output data streams. There are four possible348 output encodings, and up to four supported element sizes per encoding. Not all output encodings are349 supported for every command. The format is indicated by a 4-bit field in the CCB:350 351 Output Format Code Description352 0x0 Byte aligned, 1 byte elements353 0x1 Byte aligned, 2 byte elements354 0x2 Byte aligned, 4 byte elements355 0x3 Byte aligned, 8 byte elements356 0x4 16 byte aligned, 16 byte elements357 0x5 Reserved358 0x6 Reserved359 0x7 Reserved360 0x8 Packed vector of single bit elements361 0x9 Reserved362 0xA Reserved363 0xB Reserved364 0xC Reserved365 0xD 2 byte elements where each element is the index value of a bit,366 from an bit vector, which was 1.367 0xE 4 byte elements where each element is the index value of a bit,368 from an bit vector, which was 1.369 0xF Reserved370 37136.2.1.1.7. Application Data Integrity (ADI)372 373 On platforms which support ADI, the ADI version number may be specified for each separate memory374 access type used in the CCB command. ADI checking only occurs when reading data. When writing data,375 the specified ADI version number overwrites any existing ADI value in memory.376 377 An ADI version value of 0 or 0xF indicates the ADI checking is disabled for that data access, even if it is378 enabled in memory. By setting the appropriate flag in CCB_SUBMIT (Section 36.3.1, “ccb_submit”) it is379 also an option to disable ADI checking for all inputs accessed via virtual address for all CCBs submitted380 during that hypercall invocation.381 382 The ADI value is only guaranteed to be checked on the first 64 bytes of each data access. Mismatches on383 subsequent data chunks may not be detected, so guest software should be careful to use page size checking384 to protect against buffer overruns.385 38636.2.1.1.8. Page size checking387 388 All data accesses used in CCB commands must be bounded within a single memory page. When addresses389 are provided using a virtual address, the page size for checking is extracted from the TTE for that virtual390 address. When using real addresses, the guest must supply the page size in the same field as the address391 value. The page size must be one of the sizes supported by the underlying virtual machine. Using a value392 that is not supported may result in the CCB submission being rejected or the generation of a CCB parsing393 error in the completion area.394 395 396 515397 Coprocessor services398 399 40036.2.1.2. Extract command401 402 Converts an input vector in one format to an output vector in another format. All input format types are403 supported.404 405 The only supported output format is a padded, byte-aligned output stream, using output codes 0x0 - 0x4.406 When the specified output element size is larger than the extracted input element size, zeros are padded to407 the extracted input element. First, if the decompressed input size is not a whole number of bytes, 0 bits are408 padded to the most significant bit side till the next byte boundary. Next, if the output element size is larger409 than the byte padded input element, bytes of value 0 are added based on the Padding Direction bit in the410 CCB. If the output element size is smaller than the byte-padded input element size, the input element is411 truncated by dropped from the least significant byte side until the selected output size is reached.412 413 The return value of the CCB completion area is invalid. The “number of elements processed” field in the414 CCB completion area will be valid.415 416 The extract CCB is a 64-byte “short format” CCB.417 418 The extract CCB command format can be specified by the following packed C structure for a big-endian419 machine:420 421 422 struct extract_ccb {423 uint32_t header;424 uint32_t control;425 uint64_t completion;426 uint64_t primary_input;427 uint64_t data_access_control;428 uint64_t secondary_input;429 uint64_t reserved;430 uint64_t output;431 uint64_t table;432 };433 434 435 The exact field offsets, sizes, and composition are as follows:436 437 Offset Size Field Description438 0 4 CCB header (Table 36.1, “CCB Header Format”)439 4 4 Command control440 Bits Field Description441 [31:28] Primary Input Format (see Section 36.2.1.1.1, “Primary Input442 Format”)443 [27:23] Primary Input Element Size (see Section 36.2.1.1.2, “Primary444 Input Element Size”)445 [22:20] Primary Input Starting Offset (see Section 36.2.1.1.5, “Input446 Element Offsets”)447 [19] Secondary Input Format (see Section 36.2.1.1.3, “Secondary448 Input Format”)449 [18:16] Secondary Input Starting Offset (see Section 36.2.1.1.5, “Input450 Element Offsets”)451 452 453 516454 Coprocessor services455 456 457Offset Size Field Description458 Bits Field Description459 [15:14] Secondary Input Element Size (see Section 36.2.1.1.4,460 “Secondary Input Element Size”461 [13:10] Output Format (see Section 36.2.1.1.6, “Output Format”)462 [9] Padding Direction selector: A value of 1 causes padding bytes463 to be added to the left side of output elements. A value of 0464 causes padding bytes to be added to the right side of output465 elements.466 [8:0] Reserved4678 8 Completion468 Bits Field Description469 [63:60] ADI version (see Section 36.2.1.1.7, “Application Data470 Integrity (ADI)”)471 [59] If set to 1, a virtual device interrupt will be generated using472 the device interrupt number specified in the lower bits of this473 completion word. If 0, the lower bits of this completion word474 are ignored.475 [58:6] Completion area address bits [58:6]. Address type is476 determined by CCB header.477 [5:0] Virtual device interrupt number for completion interrupt, if478 enabled.47916 8 Primary Input480 Bits Field Description481 [63:60] ADI version (see Section 36.2.1.1.7, “Application Data482 Integrity (ADI)”)483 [59:56] If using real address, these bits should be filled in with the484 page size code for the page boundary checking the guest wants485 the virtual machine to use when accessing this data stream486 (checking is only guaranteed to be performed when using API487 version 1.1 and later). If using a virtual address, this field will488 be used as as primary input address bits [59:56].489 [55:0] Primary input address bits [55:0]. Address type is determined490 by CCB header.49124 8 Data Access Control492 Bits Field Description493 [63:62] Flow Control494 Value Description495 0b'00 Disable flow control496 0b'01 Enable flow control (only valid with "ORCL,sun4v-497 dax-fc" compatible virtual device variants)498 0b'10 Reserved499 0b'11 Reserved500 [61:60] Reserved (API 1.0)501 502 503 517504 Coprocessor services505 506 507Offset Size Field Description508 Bits Field Description509 Pipeline target (API 2.0)510 Value Description511 0b'00 Connect to primary input512 0b'01 Connect to secondary input513 0b'10 Reserved514 0b'11 Reserved515 [59:40] Output buffer size given in units of 64 bytes, minus 1. Value of516 0 means 64 bytes, value of 1 means 128 bytes, etc. Buffer size is517 only enforced if flow control is enabled in Flow Control field.518 [39:32] Reserved519 [31:30] Output Data Cache Allocation520 Value Description521 0b'00 Do not allocate cache lines for output data stream.522 0b'01 Force cache lines for output data stream to be523 allocated in the cache that is local to the submitting524 virtual cpu.525 0b'10 Allocate cache lines for output data stream, but allow526 existing cache lines associated with the data to remain527 in their current cache instance. Any memory not528 already in cache will be allocated in the cache local529 to the submitting virtual cpu.530 0b'11 Reserved531 [29:26] Reserved532 [25:24] Primary Input Length Format533 Value Description534 0b'00 Number of primary symbols535 0b'01 Number of primary bytes536 0b'10 Number of primary bits537 0b'11 Reserved538 [23:0] Primary Input Length539 Format Field Value540 # of primary symbols Number of input elements to process,541 minus 1. Command execution stops542 once count is reached.543 # of primary bytes Number of input bytes to process,544 minus 1. Command execution stops545 once count is reached. The count is546 done before any decompression or547 decoding.548 # of primary bits Number of input bits to process,549 minus 1. Command execution stops550 551 552 553 518554 Coprocessor services555 556 557 Offset Size Field Description558 Bits Field Description559 Format Field Value560 once count is reached. The count is561 done before any decompression or562 decoding, and does not include any563 bits skipped by the Primary Input564 Offset field value of the command565 control word.566 32 8 Secondary Input, if used by Primary Input Format. Same fields as Primary567 Input.568 40 8 Reserved569 48 8 Output (same fields as Primary Input)570 56 8 Symbol Table (if used by Primary Input)571 Bits Field Description572 [63:60] ADI version (see Section 36.2.1.1.7, “Application Data573 Integrity (ADI)”)574 [59:56] If using real address, these bits should be filled in with the575 page size code for the page boundary checking the guest wants576 the virtual machine to use when accessing this data stream577 (checking is only guaranteed to be performed when using API578 version 1.1 and later). If using a virtual address, this field will579 be used as as symbol table address bits [59:56].580 [55:4] Symbol table address bits [55:4]. Address type is determined581 by CCB header.582 [3:0] Symbol table version583 Value Description584 0 Huffman encoding. Must use 64 byte aligned table585 address. (Only available when using version 0 CCBs)586 1 OZIP encoding. Must use 16 byte aligned table587 address. (Only available when using version 1 CCBs)588 589 59036.2.1.3. Scan commands591 592 The scan commands search a stream of input data elements for values which match the selection criteria.593 All the input format types are supported. There are multiple formats for the scan commands, allowing the594 scan to search for exact matches to one value, exact matches to either of two values, or any value within595 a specified range. The specific type of scan is indicated by the command code in the CCB header. For the596 scan 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.598 599 There are two supported formats for the output stream: the bit vector and index array formats (codes 0x8,600 0xD, and 0xE). For the standard scan command using the bit vector output, for each input element there601 exists one bit in the vector that is set if the input element matched the scan criteria, or clear if not. The602 inverted scan command inverts the polarity of the bits in the output. The most significant bit of the first603 byte of the output stream corresponds to the first element in the input stream. The standard index array604 output format contains one array entry for each input element that matched the scan criteria. Each array605 606 607 608 519609 Coprocessor services610 611 612entry is the index of an input element that matched the scan criteria. An inverted scan command produces613a similar array, but of all the input elements which did NOT match the scan criteria.614 615The return value of the CCB completion area contains the number of input elements found which match616the scan criteria (or number that did not match for the inverted scans). The “number of elements processed”617field in the CCB completion area will be valid, indicating the number of input elements processed.618 619These commands are 128-byte “long format” CCBs.620 621The scan CCB command format can be specified by the following packed C structure for a big-endian622machine:623 624 625 struct scan_ccb {626 uint32_t header;627 uint32_t control;628 uint64_t completion;629 uint64_t primary_input;630 uint64_t data_access_control;631 uint64_t secondary_input;632 uint64_t match_criteria0;633 uint64_t output;634 uint64_t table;635 uint64_t match_criteria1;636 uint64_t match_criteria2;637 uint64_t match_criteria3;638 uint64_t reserved[5];639 };640 641 642The exact field offsets, sizes, and composition are as follows:643 644Offset Size Field Description6450 4 CCB header (Table 36.1, “CCB Header Format”)6464 4 Command control647 Bits Field Description648 [31:28] Primary Input Format (see Section 36.2.1.1.1, “Primary Input649 Format”)650 [27:23] Primary Input Element Size (see Section 36.2.1.1.2, “Primary651 Input Element Size”)652 [22:20] Primary Input Starting Offset (see Section 36.2.1.1.5, “Input653 Element Offsets”)654 [19] Secondary Input Format (see Section 36.2.1.1.3, “Secondary655 Input Format”)656 [18:16] Secondary Input Starting Offset (see Section 36.2.1.1.5, “Input657 Element Offsets”)658 [15:14] Secondary Input Element Size (see Section 36.2.1.1.4,659 “Secondary Input Element Size”660 [13:10] Output Format (see Section 36.2.1.1.6, “Output Format”)661 [9:5] Operand size for first scan criteria value. In a scan value662 operation, this is one of two potential exact match values.663 In a scan range operation, this is the size of the upper range664 665 666 520667 Coprocessor services668 669 670Offset Size Field Description671 Bits Field Description672 boundary. The value of this field is the number of bytes in the673 operand, minus 1. Values 0xF-0x1E are reserved. A value of674 0x1F indicates this operand is not in use for this scan operation.675 [4:0] Operand size for second scan criteria value. In a scan value676 operation, this is one of two potential exact match values.677 In a scan range operation, this is the size of the lower range678 boundary. The value of this field is the number of bytes in the679 operand, minus 1. Values 0xF-0x1E are reserved. A value of680 0x1F indicates this operand is not in use for this scan operation.6818 8 Completion (same fields as Section 36.2.1.2, “Extract command”)68216 8 Primary Input (same fields as Section 36.2.1.2, “Extract command”)68324 8 Data Access Control (same fields as Section 36.2.1.2, “Extract command”)68432 8 Secondary Input, if used by Primary Input Format. Same fields as Primary685 Input.68640 4 Most significant 4 bytes of first scan criteria operand. If first operand is less687 than 4 bytes, the value is left-aligned to the lowest address bytes.68844 4 Most significant 4 bytes of second scan criteria operand. If second operand689 is less than 4 bytes, the value is left-aligned to the lowest address bytes.69048 8 Output (same fields as Primary Input)69156 8 Symbol Table (if used by Primary Input). Same fields as Section 36.2.1.2,692 “Extract command”69364 4 Next 4 most significant bytes of first scan criteria operand occurring after the694 bytes specified at offset 40, if needed by the operand size. If first operand695 is less than 8 bytes, the valid bytes are left-aligned to the lowest address.69668 4 Next 4 most significant bytes of second scan criteria operand occurring after697 the bytes specified at offset 44, if needed by the operand size. If second698 operand is less than 8 bytes, the valid bytes are left-aligned to the lowest699 address.70072 4 Next 4 most significant bytes of first scan criteria operand occurring after the701 bytes specified at offset 64, if needed by the operand size. If first operand702 is less than 12 bytes, the valid bytes are left-aligned to the lowest address.70376 4 Next 4 most significant bytes of second scan criteria operand occurring after704 the bytes specified at offset 68, if needed by the operand size. If second705 operand is less than 12 bytes, the valid bytes are left-aligned to the lowest706 address.70780 4 Next 4 most significant bytes of first scan criteria operand occurring after the708 bytes specified at offset 72, if needed by the operand size. If first operand709 is less than 16 bytes, the valid bytes are left-aligned to the lowest address.71084 4 Next 4 most significant bytes of second scan criteria operand occurring after711 the bytes specified at offset 76, if needed by the operand size. If second712 operand is less than 16 bytes, the valid bytes are left-aligned to the lowest713 address.714 715 716 717 718 521719 Coprocessor services720 721 72236.2.1.4. Translate commands723 724 The translate commands takes an input array of indices, and a table of single bit values indexed by those725 indices, and outputs a bit vector or index array created by reading the tables bit value at each index in726 the input array. The output should therefore contain exactly one bit per index in the input data stream,727 when outputting as a bit vector. When outputting as an index array, the number of elements depends on the728 values read in the bit table, but will always be less than, or equal to, the number of input elements. Only729 a restricted subset of the possible input format types are supported. No variable width or Huffman/OZIP730 encoded input streams are allowed. The primary input data element size must be 3 bytes or less.731 732 The maximum table index size allowed is 15 bits, however, larger input elements may be used to provide733 additional processing of the output values. If 2 or 3 byte values are used, the least significant 15 bits are734 used as an index into the bit table. The most significant 9 bits (when using 3-byte input elements) or single735 bit (when using 2-byte input elements) are compared against a fixed 9-bit test value provided in the CCB.736 If the values match, the value from the bit table is used as the output element value. If the values do not737 match, the output data element value is forced to 0.738 739 In the inverted translate operation, the bit value read from bit table is inverted prior to its use. The additional740 additional processing based on any additional non-index bits remains unchanged, and still forces the output741 element value to 0 on a mismatch. The specific type of translate command is indicated by the command742 code in the CCB header.743 744 There are two supported formats for the output stream: the bit vector and index array formats (codes 0x8,745 0xD, and 0xE). The index array format is an array of indices of bits which would have been set if the746 output format was a bit array.747 748 The return value of the CCB completion area contains the number of bits set in the output bit vector,749 or number of elements in the output index array. The “number of elements processed” field in the CCB750 completion area will be valid, indicating the number of input elements processed.751 752 These commands are 64-byte “short format” CCBs.753 754 The translate CCB command format can be specified by the following packed C structure for a big-endian755 machine:756 757 758 struct translate_ccb {759 uint32_t header;760 uint32_t control;761 uint64_t completion;762 uint64_t primary_input;763 uint64_t data_access_control;764 uint64_t secondary_input;765 uint64_t reserved;766 uint64_t output;767 uint64_t table;768 };769 770 771 The exact field offsets, sizes, and composition are as follows:772 773 774 Offset Size Field Description775 0 4 CCB header (Table 36.1, “CCB Header Format”)776 777 778 522779 Coprocessor services780 781 782Offset Size Field Description7834 4 Command control784 Bits Field Description785 [31:28] Primary Input Format (see Section 36.2.1.1.1, “Primary Input786 Format”)787 [27:23] Primary Input Element Size (see Section 36.2.1.1.2, “Primary788 Input Element Size”)789 [22:20] Primary Input Starting Offset (see Section 36.2.1.1.5, “Input790 Element Offsets”)791 [19] Secondary Input Format (see Section 36.2.1.1.3, “Secondary792 Input Format”)793 [18:16] Secondary Input Starting Offset (see Section 36.2.1.1.5, “Input794 Element Offsets”)795 [15:14] Secondary Input Element Size (see Section 36.2.1.1.4,796 “Secondary Input Element Size”797 [13:10] Output Format (see Section 36.2.1.1.6, “Output Format”)798 [9] Reserved799 [8:0] Test value used for comparison against the most significant bits800 in the input values, when using 2 or 3 byte input elements.8018 8 Completion (same fields as Section 36.2.1.2, “Extract command”80216 8 Primary Input (same fields as Section 36.2.1.2, “Extract command”80324 8 Data Access Control (same fields as Section 36.2.1.2, “Extract command”,804 except Primary Input Length Format may not use the 0x0 value)80532 8 Secondary Input, if used by Primary Input Format. Same fields as Primary806 Input.80740 8 Reserved80848 8 Output (same fields as Primary Input)80956 8 Bit Table810 Bits Field Description811 [63:60] ADI version (see Section 36.2.1.1.7, “Application Data812 Integrity (ADI)”)813 [59:56] If using real address, these bits should be filled in with the814 page size code for the page boundary checking the guest wants815 the virtual machine to use when accessing this data stream816 (checking is only guaranteed to be performed when using API817 version 1.1 and later). If using a virtual address, this field will818 be used as as bit table address bits [59:56]819 [55:4] Bit table address bits [55:4]. Address type is determined by820 CCB header. Address must be 64-byte aligned (CCB version821 0) or 16-byte aligned (CCB version 1).822 [3:0] Bit table version823 Value Description824 0 4KB table size825 1 8KB table size826 827 828 829 523830 Coprocessor services831 832 83336.2.1.5. Select command834 The select command filters the primary input data stream by using a secondary input bit vector to determine835 which input elements to include in the output. For each bit set at a given index N within the bit vector,836 the Nth input element is included in the output. If the bit is not set, the element is not included. Only a837 restricted subset of the possible input format types are supported. No variable width or run length encoded838 input streams are allowed, since the secondary input stream is used for the filtering bit vector.839 840 The only supported output format is a padded, byte-aligned output stream. The stream follows the same841 rules and restrictions as padded output stream described in Section 36.2.1.2, “Extract command”.842 843 The return value of the CCB completion area contains the number of bits set in the input bit vector. The844 "number of elements processed" field in the CCB completion area will be valid, indicating the number845 of input elements processed.846 847 The select CCB is a 64-byte “short format” CCB.848 849 The select CCB command format can be specified by the following packed C structure for a big-endian850 machine:851 852 853 struct select_ccb {854 uint32_t header;855 uint32_t control;856 uint64_t completion;857 uint64_t primary_input;858 uint64_t data_access_control;859 uint64_t secondary_input;860 uint64_t reserved;861 uint64_t output;862 uint64_t table;863 };864 865 866 The exact field offsets, sizes, and composition are as follows:867 868 Offset Size Field Description869 0 4 CCB header (Table 36.1, “CCB Header Format”)870 4 4 Command control871 Bits Field Description872 [31:28] Primary Input Format (see Section 36.2.1.1.1, “Primary Input873 Format”)874 [27:23] Primary Input Element Size (see Section 36.2.1.1.2, “Primary875 Input Element Size”)876 [22:20] Primary Input Starting Offset (see Section 36.2.1.1.5, “Input877 Element Offsets”)878 [19] Secondary Input Format (see Section 36.2.1.1.3, “Secondary879 Input Format”)880 [18:16] Secondary Input Starting Offset (see Section 36.2.1.1.5, “Input881 Element Offsets”)882 [15:14] Secondary Input Element Size (see Section 36.2.1.1.4,883 “Secondary Input Element Size”884 885 886 524887 Coprocessor services888 889 890 Offset Size Field Description891 Bits Field Description892 [13:10] Output Format (see Section 36.2.1.1.6, “Output Format”)893 [9] Padding Direction selector: A value of 1 causes padding bytes894 to be added to the left side of output elements. A value of 0895 causes padding bytes to be added to the right side of output896 elements.897 [8:0] Reserved898 8 8 Completion (same fields as Section 36.2.1.2, “Extract command”899 16 8 Primary Input (same fields as Section 36.2.1.2, “Extract command”900 24 8 Data Access Control (same fields as Section 36.2.1.2, “Extract command”)901 32 8 Secondary Bit Vector Input. Same fields as Primary Input.902 40 8 Reserved903 48 8 Output (same fields as Primary Input)904 56 8 Symbol Table (if used by Primary Input). Same fields as Section 36.2.1.2,905 “Extract command”906 90736.2.1.6. No-op and Sync commands908 The no-op (no operation) command is a CCB which has no processing effect. The CCB, when processed909 by the virtual machine, simply updates the completion area with its execution status. The CCB may have910 the serial-conditional flags set in order to restrict when it executes.911 912 The sync command is a variant of the no-op command which with restricted execution timing. A sync913 command CCB will only execute when all previous commands submitted in the same request have914 completed. This is stronger than the conditional flag sequencing, which is only dependent on a single915 previous serial CCB. While the relative ordering is guaranteed, virtual machine implementations with916 shared hardware resources may cause the sync command to wait for longer than the minimum required917 time.918 919 The return value of the CCB completion area is invalid for these CCBs. The “number of elements920 processed” field is also invalid for these CCBs.921 922 These commands are 64-byte “short format” CCBs.923 924 The no-op CCB command format can be specified by the following packed C structure for a big-endian925 machine:926 927 928 struct nop_ccb {929 uint32_t header;930 uint32_t control;931 uint64_t completion;932 uint64_t reserved[6];933 };934 935 936 The exact field offsets, sizes, and composition are as follows:937 938 Offset Size Field Description939 0 4 CCB header (Table 36.1, “CCB Header Format”)940 941 942 525943 Coprocessor services944 945 946 Offset Size Field Description947 4 4 Command control948 Bits Field Description949 [31] If set, this CCB functions as a Sync command. If clear, this950 CCB functions as a No-op command.951 [30:0] Reserved952 8 8 Completion (same fields as Section 36.2.1.2, “Extract command”953 16 46 Reserved954 95536.2.2. CCB Completion Area956 All CCB commands use a common 128-byte Completion Area format, which can be specified by the957 following packed C structure for a big-endian machine:958 959 960 struct completion_area {961 uint8_t status_flag;962 uint8_t error_note;963 uint8_t rsvd0[2];964 uint32_t error_values;965 uint32_t output_size;966 uint32_t rsvd1;967 uint64_t run_time;968 uint64_t run_stats;969 uint32_t elements;970 uint8_t rsvd2[20];971 uint64_t return_value;972 uint64_t extra_return_value[8];973 };974 975 976 The Completion Area must be a 128-byte aligned memory location. The exact layout can be described977 using byte offsets and sizes relative to the memory base:978 979 Offset Size Field Description980 0 1 CCB execution status981 0x0 Command not yet completed982 0x1 Command ran and succeeded983 0x2 Command ran and failed (partial results may be been984 produced)985 0x3 Command ran and was killed (partial execution may986 have occurred)987 0x4 Command was not run988 0x5-0xF Reserved989 1 1 Error reason code990 0x0 Reserved991 0x1 Buffer overflow992 993 994 526995 Coprocessor services996 997 998Offset Size Field Description999 0x2 CCB decoding error1000 0x3 Page overflow1001 0x4-0x6 Reserved1002 0x7 Command was killed1003 0x8 Command execution timeout1004 0x9 ADI miscompare error1005 0xA Data format error1006 0xB-0xD Reserved1007 0xE Unexpected hardware error (Do not retry)1008 0xF Unexpected hardware error (Retry is ok)1009 0x10-0x7F Reserved1010 0x80 Partial Symbol Warning1011 0x81-0xFF Reserved10122 2 Reserved10134 4 If a partial symbol warning was generated, this field contains the number1014 of remaining bits which were not decoded.10158 4 Number of bytes of output produced101612 4 Reserved101716 8 Runtime of command (unspecified time units)101824 8 Reserved101932 4 Number of elements processed102036 20 Reserved102156 8 Return value102264 64 Extended return value1023 1024The CCB completion area should be treated as read-only by guest software. The CCB execution status1025byte will be cleared by the Hypervisor to reflect the pending execution status when the CCB is submitted1026successfully. All other fields are considered invalid upon CCB submission until the CCB execution status1027byte becomes non-zero.1028 1029CCBs which complete with status 0x2 or 0x3 may produce partial results and/or side effects due to partial1030execution of the CCB command. Some valid data may be accessible depending on the fault type, however,1031it is recommended that guest software treat the destination buffer as being in an unknown state. If a CCB1032completes with a status byte of 0x2, the error reason code byte can be read to determine what corrective1033action should be taken.1034 1035A buffer overflow indicates that the results of the operation exceeded the size of the output buffer indicated1036in the CCB. The operation can be retried by resubmitting the CCB with a larger output buffer.1037 1038A CCB decoding error indicates that the CCB contained some invalid field values. It may be also be1039triggered if the CCB output is directed at a non-existent secondary input and the pipelining hint is followed.1040 1041A page overflow error indicates that the operation required accessing a memory location beyond the page1042size associated with a given address. No data will have been read or written past the page boundary, but1043partial results may have been written to the destination buffer. The CCB can be resubmitted with a larger1044page size memory allocation to complete the operation.1045 1046 1047 5271048 Coprocessor services1049 1050 1051 In the case of pipelined CCBs, a page overflow error will be triggered if the output from the pipeline source1052 CCB ends before the input of the pipeline target CCB. Page boundaries are ignored when the pipeline1053 hint is followed.1054 1055 Command kill indicates that the CCB execution was halted or prevented by use of the ccb_kill API call.1056 1057 Command timeout indicates that the CCB execution began, but did not complete within a pre-determined1058 limit set by the virtual machine. The command may have produced some or no output. The CCB may be1059 resubmitted with no alterations.1060 1061 ADI miscompare indicates that the memory buffer version specified in the CCB did not match the value1062 in memory when accessed by the virtual machine. Guest software should not attempt to resubmit the CCB1063 without determining the cause of the version mismatch.1064 1065 A data format error indicates that the input data stream did not follow the specified data input formatting1066 selected in the CCB.1067 1068 Some CCBs which encounter hardware errors may be resubmitted without change. Persistent hardware1069 errors may result in multiple failures until RAS software can identify and isolate the faulty component.1070 1071 The output size field indicates the number of bytes of valid output in the destination buffer. This field is1072 not valid for all possible CCB commands.1073 1074 The runtime field indicates the execution time of the CCB command once it leaves the internal virtual1075 machine queue. The time units are fixed, but unspecified, allowing only relative timing comparisons1076 by guest software. The time units may also vary by hardware platform, and should not be construed to1077 represent any absolute time value.1078 1079 Some data query commands process data in units of elements. If applicable to the command, the number of1080 elements processed is indicated in the listed field. This field is not valid for all possible CCB commands.1081 1082 The return value and extended return value fields are output locations for commands which do not use1083 a destination output buffer, or have secondary return results. The field is not valid for all possible CCB1084 commands.1085 108636.3. Hypervisor API Functions108736.3.1. ccb_submit1088 trap# FAST_TRAP1089 function# CCB_SUBMIT1090 arg0 address1091 arg1 length1092 arg2 flags1093 arg3 reserved1094 ret0 status1095 ret1 length1096 ret2 status data1097 ret3 reserved1098 1099 Submit one or more coprocessor control blocks (CCBs) for evaluation and processing by the virtual1100 machine. The CCBs are passed in a linear array indicated by address. length indicates the size of1101 the array in bytes.1102 1103 1104 5281105 Coprocessor services1106 1107 1108The address should be aligned to the size indicated by length, rounded up to the nearest power of1109two. Virtual machines implementations may reject submissions which do not adhere to that alignment.1110length must be a multiple of 64 bytes. If length is zero, the maximum supported array length will be1111returned as length in ret1. In all other cases, the length value in ret1 will reflect the number of bytes1112successfully consumed from the input CCB array.1113 1114 Implementation note1115 Virtual machines should never reject submissions based on the alignment of address if the1116 entire array is contained within a single memory page of the smallest page size supported by the1117 virtual machine.1118 1119A guest may choose to submit addresses used in this API function, including the CCB array address,1120as either a real or virtual addresses, with the type of each address indicated in flags. Virtual addresses1121must be present in either the TLB or an active TSB to be processed. The translation context for virtual1122addresses is determined by a combination of CCB contents and the flags argument.1123 1124The flags argument is divided into multiple fields defined as follows:1125 1126 1127Bits Field Description1128[63:16] Reserved1129[15] Disable ADI for VA reads (in API 2.0)1130 Reserved (in API 1.0)1131[14] Virtual addresses within CCBs are translated in privileged context1132[13:12] Alternate translation context for virtual addresses within CCBs:1133 0b'00 CCBs requesting alternate context are rejected1134 0b'01 Reserved1135 0b'10 CCBs requesting alternate context use secondary context1136 0b'11 CCBs requesting alternate context use nucleus context1137[11:9] Reserved1138[8] Queue info flag1139[7] All-or-nothing flag1140[6] If address is a virtual address, treat its translation context as privileged1141[5:4] Address type of address:1142 0b'00 Real address1143 0b'01 Virtual address in primary context1144 0b'10 Virtual address in secondary context1145 0b'11 Virtual address in nucleus context1146[3:2] Reserved1147[1:0] CCB command type:1148 0b'00 Reserved1149 0b'01 Reserved1150 0b'10 Query command1151 0b'11 Reserved1152 1153 1154 1155 5291156 Coprocessor services1157 1158 1159 The CCB submission type and address type for the CCB array must be provided in the flags argument.1160 All other fields are optional values which change the default behavior of the CCB processing.1161 1162 When set to one, the "Disable ADI for VA reads" bit will turn off ADI checking when using a virtual1163 address to load data. ADI checking will still be done when loading real-addressed memory. This bit is only1164 available when using major version 2 of the coprocessor API group; at major version 1 it is reserved. For1165 more information about using ADI and DAX, see Section 36.2.1.1.7, “Application Data Integrity (ADI)”.1166 1167 By default, all virtual addresses are treated as user addresses. If the virtual address translations are1168 privileged, they must be marked as such in the appropriate flags field. The virtual addresses used within1169 the submitted CCBs must all be translated with the same privilege level.1170 1171 By default, all virtual addresses used within the submitted CCBs are translated using the primary context1172 active at the time of the submission. The address type field within a CCB allows each address to request1173 translation in an alternate address context. The address context used when the alternate address context is1174 requested is selected in the flags argument.1175 1176 The all-or-nothing flag specifies whether the virtual machine should allow partial submissions of the1177 input CCB array. When using CCBs with serial-conditional flags, it is strongly recommended to use1178 the all-or-nothing flag to avoid broken conditional chains. Using long CCB chains on a machine under1179 high coprocessor load may make this impractical, however, and require submitting without the flag.1180 When submitting serial-conditional CCBs without the all-or-nothing flag, guest software must manually1181 implement the serial-conditional behavior at any point where the chain was not submitted in a single API1182 call, and resubmission of the remaining CCBs should clear any conditional flag that might be set in the1183 first remaining CCB. Failure to do so will produce indeterminate CCB execution status and ordering.1184 1185 When the all-or-nothing flag is not specified, callers should check the value of length in ret1 to determine1186 how many CCBs from the array were successfully submitted. Any remaining CCBs can be resubmitted1187 without modifications.1188 1189 The value of length in ret1 is also valid when the API call returns an error, and callers should always1190 check its value to determine which CCBs in the array were already processed. This will additionally1191 identify which CCB encountered the processing error, and was not submitted successfully.1192 1193 If the queue info flag is used during submission, and at least one CCB was successfully submitted, the1194 length value in ret1 will be a multi-field value defined as follows:1195 Bits Field Description1196 [63:48] DAX unit instance identifier1197 [47:32] DAX queue instance identifier1198 [31:16] Reserved1199 [15:0] Number of CCB bytes successfully submitted1200 1201 The value of status data depends on the status value. See error status code descriptions for details.1202 The value is undefined for status values that do not specifically list a value for the status data.1203 1204 The API has a reserved input and output register which will be used in subsequent minor versions of this1205 API function. Guest software implementations should treat that register as voltile across the function call1206 in order to maintain forward compatibility.1207 120836.3.1.1. Errors1209 EOK One or more CCBs have been accepted and enqueued in the virtual machine1210 and no errors were been encountered during submission. Some submitted1211 CCBs may not have been enqueued due to internal virtual machine limitations,1212 and may be resubmitted without changes.1213 1214 1215 5301216 Coprocessor services1217 1218 1219EWOULDBLOCK An internal resource conflict within the virtual machine has prevented it from1220 being able to complete the CCB submissions sufficiently quickly, requiring1221 it to abandon processing before it was complete. Some CCBs may have been1222 successfully enqueued prior to the block, and all remaining CCBs may be1223 resubmitted without changes.1224EBADALIGN CCB array is not on a 64-byte boundary, or the array length is not a multiple1225 of 64 bytes.1226ENORADDR A real address used either for the CCB array, or within one of the submitted1227 CCBs, is not valid for the guest. Some CCBs may have been enqueued prior1228 to the error being detected.1229ENOMAP A virtual address used either for the CCB array, or within one of the submitted1230 CCBs, could not be translated by the virtual machine using either the TLB1231 or TSB contents. The submission may be retried after adding the required1232 mapping, or by converting the virtual address into a real address. Due to the1233 shared nature of address translation resources, there is no theoretical limit on1234 the number of times the translation may fail, and it is recommended all guests1235 implement some real address based backup. The virtual address which failed1236 translation is returned as status data in ret2. Some CCBs may have been1237 enqueued prior to the error being detected.1238EINVAL The virtual machine detected an invalid CCB during submission, or invalid1239 input arguments, such as bad flag values. Note that not all invalid CCB values1240 will be detected during submission, and some may be reported as errors in the1241 completion area instead. Some CCBs may have been enqueued prior to the1242 error being detected. This error may be returned if the CCB version is invalid.1243ETOOMANY The request was submitted with the all-or-nothing flag set, and the array size is1244 greater than the virtual machine can support in a single request. The maximum1245 supported size for the current virtual machine can be queried by submitting a1246 request with a zero length array, as described above.1247ENOACCESS The guest does not have permission to submit CCBs, or an address used in a1248 CCBs lacks sufficient permissions to perform the required operation (no write1249 permission on the destination buffer address, for example). A virtual address1250 which fails permission checking is returned as status data in ret2. Some1251 CCBs may have been enqueued prior to the error being detected.1252EUNAVAILABLE The requested CCB operation could not be performed at this time. The1253 restricted operation availability may apply only to the first unsuccessfully1254 submitted CCB, or may apply to a larger scope. The status should not be1255 interpreted as permanent, and the guest should attempt to submit CCBs in1256 the future which had previously been unable to be performed. The status1257 data provides additional information about scope of the restricted availability1258 as follows:1259 Value Description1260 0 Processing for the exact CCB instance submitted was unavailable,1261 and it is recommended the guest emulate the operation. The1262 guest should continue to submit all other CCBs, and assume no1263 restrictions beyond this exact CCB instance.1264 1 Processing is unavailable for all CCBs using the requested opcode,1265 and it is recommended the guest emulate the operation. The1266 guest should continue to submit all other CCBs that use different1267 opcodes, but can expect continued rejections of CCBs using the1268 same opcode in the near future.1269 1270 1271 5311272 Coprocessor services1273 1274 1275 Value Description1276 2 Processing is unavailable for all CCBs using the requested CCB1277 version, and it is recommended the guest emulate the operation.1278 The guest should continue to submit all other CCBs that use1279 different CCB versions, but can expect continued rejections of1280 CCBs using the same CCB version in the near future.1281 3 Processing is unavailable for all CCBs on the submitting vcpu,1282 and it is recommended the guest emulate the operation or resubmit1283 the CCB on a different vcpu. The guest should continue to submit1284 CCBs on all other vcpus but can expect continued rejections of all1285 CCBs on this vcpu in the near future.1286 4 Processing is unavailable for all CCBs, and it is recommended1287 the guest emulate the operation. The guest should expect all CCB1288 submissions to be similarly rejected in the near future.1289 1290 129136.3.2. ccb_info1292 1293 trap# FAST_TRAP1294 function# CCB_INFO1295 arg0 address1296 ret0 status1297 ret1 CCB state1298 ret2 position1299 ret3 dax1300 ret4 queue1301 1302 Requests status information on a previously submitted CCB. The previously submitted CCB is identified1303 by the 64-byte aligned real address of the CCBs completion area.1304 1305 A CCB can be in one of 4 states:1306 1307 1308 State Value Description1309 COMPLETED 0 The CCB has been fetched and executed, and is no longer active in1310 the virtual machine.1311 ENQUEUED 1 The requested CCB is current in a queue awaiting execution.1312 INPROGRESS 2 The CCB has been fetched and is currently being executed. It may still1313 be possible to stop the execution using the ccb_kill hypercall.1314 NOTFOUND 3 The CCB could not be located in the virtual machine, and does not1315 appear to have been executed. This may occur if the CCB was lost1316 due to a hardware error, or the CCB may not have been successfully1317 submitted to the virtual machine in the first place.1318 1319 Implementation note1320 Some platforms may not be able to report CCBs that are currently being processed, and therefore1321 guest software should invoke the ccb_kill hypercall prior to assuming the request CCB will never1322 be executed because it was in the NOTFOUND state.1323 1324 1325 5321326 Coprocessor services1327 1328 1329 The position return value is only valid when the state is ENQUEUED. The value returned is the number1330 of other CCBs ahead of the requested CCB, to provide a relative estimate of when the CCB may execute.1331 1332 The dax return value is only valid when the state is ENQUEUED. The value returned is the DAX unit1333 instance identifier for the DAX unit processing the queue where the requested CCB is located. The value1334 matches the value that would have been, or was, returned by ccb_submit using the queue info flag.1335 1336 The queue return value is only valid when the state is ENQUEUED. The value returned is the DAX1337 queue instance identifier for the DAX unit processing the queue where the requested CCB is located. The1338 value matches the value that would have been, or was, returned by ccb_submit using the queue info flag.1339 134036.3.2.1. Errors1341 1342 EOK The request was processed and the CCB state is valid.1343 EBADALIGN address is not on a 64-byte aligned.1344 ENORADDR The real address provided for address is not valid.1345 EINVAL The CCB completion area contents are not valid.1346 EWOULDBLOCK Internal resource constraints prevented the CCB state from being queried at this1347 time. The guest should retry the request.1348 ENOACCESS The guest does not have permission to access the coprocessor virtual device1349 functionality.1350 135136.3.3. ccb_kill1352 1353 trap# FAST_TRAP1354 function# CCB_KILL1355 arg0 address1356 ret0 status1357 ret1 result1358 1359 Request to stop execution of a previously submitted CCB. The previously submitted CCB is identified by1360 the 64-byte aligned real address of the CCBs completion area.1361 1362 The kill attempt can produce one of several values in the result return value, reflecting the CCB state1363 and actions taken by the Hypervisor:1364 1365 Result Value Description1366 COMPLETED 0 The CCB has been fetched and executed, and is no longer active in1367 the virtual machine. It could not be killed and no action was taken.1368 DEQUEUED 1 The requested CCB was still enqueued when the kill request was1369 submitted, and has been removed from the queue. Since the CCB1370 never began execution, no memory modifications were produced by1371 it, and the completion area will never be updated. The same CCB may1372 be submitted again, if desired, with no modifications required.1373 KILLED 2 The CCB had been fetched and was being executed when the kill1374 request was submitted. The CCB execution was stopped, and the CCB1375 is no longer active in the virtual machine. The CCB completion area1376 will reflect the killed status, with the subsequent implications that1377 partial results may have been produced. Partial results may include full1378 1379 1380 5331381 Coprocessor services1382 1383 1384 Result Value Description1385 command execution if the command was stopped just prior to writing1386 to the completion area.1387 NOTFOUND 3 The CCB could not be located in the virtual machine, and does not1388 appear to have been executed. This may occur if the CCB was lost1389 due to a hardware error, or the CCB may not have been successfully1390 submitted to the virtual machine in the first place. CCBs in the state1391 are guaranteed to never execute in the future unless resubmitted.1392 139336.3.3.1. Interactions with Pipelined CCBs1394 1395 If the pipeline target CCB is killed but the pipeline source CCB was skipped, the completion area of the1396 target CCB may contain status (4,0) "Command was skipped" instead of (3,7) "Command was killed".1397 1398 If the pipeline source CCB is killed, the pipeline target CCB's completion status may read (1,0) "Success".1399 This does not mean the target CCB was processed; since the source CCB was killed, there was no1400 meaningful output on which the target CCB could operate.1401 140236.3.3.2. Errors1403 1404 EOK The request was processed and the result is valid.1405 EBADALIGN address is not on a 64-byte aligned.1406 ENORADDR The real address provided for address is not valid.1407 EINVAL The CCB completion area contents are not valid.1408 EWOULDBLOCK Internal resource constraints prevented the CCB from being killed at this time.1409 The guest should retry the request.1410 ENOACCESS The guest does not have permission to access the coprocessor virtual device1411 functionality.1412 141336.3.4. dax_info1414 trap# FAST_TRAP1415 function# DAX_INFO1416 ret0 status1417 ret1 Number of enabled DAX units1418 ret2 Number of disabled DAX units1419 1420 Returns the number of DAX units that are enabled for the calling guest to submit CCBs. The number of1421 DAX units that are disabled for the calling guest are also returned. A disabled DAX unit would have been1422 available for CCB submission to the calling guest had it not been offlined.1423 142436.3.4.1. Errors1425 1426 EOK The request was processed and the number of enabled/disabled DAX units1427 are valid.1428 1429 1430 1431 1432 5341433 1434