Lines Matching full:virtual
1 Excerpt from UltraSPARC Virtual Machine Specification
14 …se APIs may only be provided by certain platforms, and may not be available to all virtual machines
22 functionality offered may vary by virtual machine implementation.
24 …The DAX is a virtual device to sun4v guests, with supported data operations indicated by the virtu…
38 …e is no fixed limit on the number of outstanding CCBs guest software may have queued in the virtual
39 …machine, however, internal resource limitations within the virtual machine can cause CCB submissio…
44 …The availability of DAX coprocessor command service is indicated by the presence of the DAX virtual
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
49 The query functionality may vary based on the compatibility property of the virtual device:
111 36.1.2. DAX Virtual Device Interrupts
112 …The DAX virtual device has multiple interrupts associated with it which may be used by the guest if
113 …desired. The number of device interrupts available to the guest is indicated in the virtual device…
114 …guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device node”). If the de…
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
160 0b'01 Alternate context virtual address
162 0b'11 Primary context virtual address
165 0b'001 Alternate context virtual address
167 0b'011 Primary context virtual address
181 0b'001 Alternate context virtual address
183 0b'011 Primary context virtual address
190 0b'001 Alternate context virtual address
192 0b'011 Primary context virtual address
199 0b'01 Alternate context virtual address
201 0b'11 Primary context virtual address
235 …interpreted by the virtual machine. Not all of the types specified are used by every CCB format. T…
236 …ich are not applicable to the given CCB command should be indicated as type 0 (No address). Virtual
238 …for the submitting virtual processor. Virtual addresses which cannot be translated by the virtual …
239 …will result in the CCB submission being rejected, with the causal virtual address indicated. The C…
379 …also an option to disable ADI checking for all inputs accessed via virtual address for all CCBs su…
389 …are provided using a virtual address, the page size for checking is extracted from the TTE for tha…
391 …value. The page size must be one of the sizes supported by the underlying virtual machine. Using a…
471 [59] If set to 1, a virtual device interrupt will be generated using
477 [5:0] Virtual device interrupt number for completion interrupt, if
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
497 dax-fc" compatible virtual device variants)
524 virtual cpu.
529 to the submitting virtual cpu.
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
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
909 …by the virtual machine, simply updates the completion area with its execution status. The CCB may …
915 …previous serial CCB. While the relative ordering is guaranteed, virtual machine implementations wi…
1058 … limit set by the virtual machine. The command may have produced some or no output. The CCB may be
1062 …in memory when accessed by the virtual machine. Guest software should not attempt to resubmit the …
1074 …e runtime field indicates the execution time of the CCB command once it leaves the internal virtual
1099 … Submit one or more coprocessor control blocks (CCBs) for evaluation and processing by the virtual
1109 two. Virtual machines implementations may reject submissions which do not adhere to that alignment.
1115 Virtual machines should never reject submissions based on the alignment of address if the
1117 virtual machine.
1120 as either a real or virtual addresses, with the type of each address indicated in flags. Virtual ad…
1121 … be present in either the TLB or an active TSB to be processed. The translation context for virtual
1131 [14] Virtual addresses within CCBs are translated in privileged context
1132 [13:12] Alternate translation context for virtual addresses within CCBs:
1140 [6] If address is a virtual address, treat its translation context as privileged
1143 0b'01 Virtual address in primary context
1144 0b'10 Virtual address in secondary context
1145 0b'11 Virtual address in nucleus context
1162 …When set to one, the "Disable ADI for VA reads" bit will turn off ADI checking when using a virtual
1167 …By default, all virtual addresses are treated as user addresses. If the virtual address translatio…
1168 …privileged, they must be marked as such in the appropriate flags field. The virtual addresses used…
1171 …By default, all virtual addresses used within the submitted CCBs are translated using the primary …
1176 …The all-or-nothing flag specifies whether the virtual machine should allow partial submissions of …
1209 … EOK One or more CCBs have been accepted and enqueued in the virtual machine
1211 … CCBs may not have been enqueued due to internal virtual machine limitations,
1219 EWOULDBLOCK An internal resource conflict within the virtual machine has prevented it from
1229 ENOMAP A virtual address used either for the CCB array, or within one of the submitted
1230 CCBs, could not be translated by the virtual machine using either the TLB
1232 mapping, or by converting the virtual address into a real address. Due to the
1235 implement some real address based backup. The virtual address which failed
1238 EINVAL The virtual machine detected an invalid CCB during submission, or invalid
1244 greater than the virtual machine can support in a single request. The maximum
1245 supported size for the current virtual machine can be queried by submitting a
1249 permission on the destination buffer address, for example). A virtual address
1310 the virtual machine.
1314 …NOTFOUND 3 The CCB could not be located in the virtual machine, and doe…
1317 submitted to the virtual machine in the first place.
1348 …OACCESS The guest does not have permission to access the coprocessor virtual device
1367 … the virtual machine. It could not be killed and no action was taken.
1375 … is no longer active in the virtual machine. The CCB completion area
1387 …NOTFOUND 3 The CCB could not be located in the virtual machine, and does n…
1390 … submitted to the virtual machine in the first place. CCBs in the state
1410 …ACCESS The guest does not have permission to access the coprocessor virtual device