Home
last modified time | relevance | path

Searched full:virtual (Results 1 – 25 of 3163) sorted by relevance

12345678910>>...127

/kernel/linux/linux-5.10/net/vmw_vsock/
DKconfig7 tristate "Virtual Socket protocol"
9 Virtual Socket Protocol is a socket protocol similar to TCP/IP
10 allowing communication between Virtual Machines and hypervisor
20 tristate "Virtual Sockets monitoring interface"
30 tristate "Virtual Sockets loopback transport"
35 This module implements a loopback transport for Virtual Sockets,
42 tristate "VMware VMCI transport for Virtual Sockets"
45 This module implements a VMCI transport for Virtual Sockets.
47 Enable this transport if your Virtual Machine runs on a VMware
54 tristate "virtio transport for Virtual Sockets"
[all …]
/kernel/linux/linux-5.10/drivers/staging/unisys/Documentation/
Doverview.txt19 visorbus to present the virtual busses involved. Drivers in the 'visor*'
29 as the "service partition", "IO partition" (for virtual network and scsi disk
30 devices), or "console partition" (for virtual keyboard and mouse devices).
32 Each virtual device requires exactly 1 dedicated channel, which the guest
59 The visorbus driver handles the virtual busses on which all of the virtual
72 visorbus can similarly force auto-loading of function drivers for virtual
74 form in the hotplug uevent environment when each virtual device is
83 The actual struct device objects that correspond to each virtual bus and
84 each virtual device are created and owned by visorbus. These device objects
104 * the addresses of callback functions to be called whenever a virtual
[all …]
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Dio.c70 .virtual = L3_24XX_VIRT,
76 .virtual = L4_24XX_VIRT,
86 .virtual = DSP_MEM_2420_VIRT,
92 .virtual = DSP_IPI_2420_VIRT,
98 .virtual = DSP_MMU_2420_VIRT,
110 .virtual = L4_WK_243X_VIRT,
116 .virtual = OMAP243X_GPMC_VIRT,
122 .virtual = OMAP243X_SDRC_VIRT,
128 .virtual = OMAP243X_SMS_VIRT,
140 .virtual = L3_34XX_VIRT,
[all …]
/kernel/linux/linux-5.10/Documentation/sparc/oradax/
Ddax-hv-api.txt1 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 …he availablility 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
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/gvt/
Dvgpu.c208 * intel_gvt_active_vgpu - activate a virtual GPU
209 * @vgpu: virtual GPU
211 * This function is called when user wants to activate a virtual GPU.
222 * intel_gvt_deactive_vgpu - deactivate a virtual GPU
223 * @vgpu: virtual GPU
225 * This function is called when user wants to deactivate a virtual GPU.
226 * The virtual GPU will be stopped.
247 * intel_gvt_release_vgpu - release a virtual GPU
248 * @vgpu: virtual GPU
250 * This function is called when user wants to release a virtual GPU.
[all …]
/kernel/linux/linux-5.10/drivers/misc/habanalabs/common/
Dmemory.c20 * device virtual memory.
24 * virtual range which is a half of the total device virtual range.
26 * On each mapping of physical pages, a suitable virtual range chunk (with a
31 * On each Unmapping of a virtual address, the relevant virtual chunk is
37 * virtual range (which is a half of the device total virtual range).
166 * dma_map_host_va - DMA mapping of the given host virtual address.
168 * @addr: the host virtual address of the memory area
220 * dma_unmap_host_va - DMA unmapping of the given host virtual address.
345 * clear_va_list_locked - free virtual addresses list
348 * @va_list : list of virtual addresses to free
[all …]
/kernel/linux/linux-5.10/Documentation/x86/
Dsva.rst4 Shared Virtual Addressing (SVA) with ENQCMD
10 Shared Virtual Addressing (SVA) allows the processor and device to use the
11 same virtual addresses avoiding the need for software to translate virtual
12 addresses to physical addresses. SVA is what PCIe calls Shared Virtual
15 In addition to the convenience of using application virtual addresses
24 to cache translations for virtual addresses. The IOMMU driver uses the
26 sync. When an ATS lookup fails for a virtual address, the device should
27 use the PRI in order to request the virtual address to be paged into the
35 the use of Shared Work Queues (SWQ) by both applications and Virtual
52 performed, virtual addresses of all parameters, virtual address of a completion
[all …]
/kernel/linux/linux-5.10/sound/isa/wavefront/
Dwavefront_midi.c14 * "Virtual MIDI" mode. In this mode, there are effectively *two*
31 * NOTE: VIRTUAL MIDI MODE IS ON BY DEFAULT (see lowlevel/isa/wavefront.c)
33 * The main reason to turn off Virtual MIDI mode is when you want to
39 * The main reason to turn on Virtual MIDI Mode is to provide two
145 spin_lock_irqsave (&midi->virtual, flags); in snd_wavefront_midi_output_write()
147 spin_unlock_irqrestore (&midi->virtual, flags); in snd_wavefront_midi_output_write()
163 spin_unlock_irqrestore (&midi->virtual, flags); in snd_wavefront_midi_output_write()
167 spin_unlock_irqrestore (&midi->virtual, flags); in snd_wavefront_midi_output_write()
170 spin_unlock_irqrestore (&midi->virtual, flags); in snd_wavefront_midi_output_write()
188 spin_lock_irqsave (&midi->virtual, flags); in snd_wavefront_midi_output_write()
[all …]
/kernel/linux/linux-5.10/Documentation/arm/
Dporting.rst12 virtual address to a physical address. Normally, it is simply:
22 virtual or physical addresses here, since the MMU will be off at
48 Virtual address of the initial RAM disk. The following constraint
65 Virtual start address of the first bank of RAM. During the kernel
66 boot phase, virtual address PAGE_OFFSET will be mapped to physical
76 Any virtual address below TASK_SIZE is deemed to be user process
87 Virtual start address of kernel, normally PAGE_OFFSET + 0x8000.
93 Virtual address for the kernel data segment. Must not be defined
97 Virtual addresses bounding the vmalloc() area. There must not be
101 last virtual RAM address (found using variable high_memory).
[all …]
/kernel/linux/linux-5.10/arch/arm/mm/
Dcache-v4wb.S146 * - start - virtual start address
147 * - end - virtual end address
159 * - start - virtual start address
160 * - end - virtual end address
178 * Invalidate (discard) the specified virtual address range.
183 * - start - virtual start address
184 * - end - virtual end address
202 * Clean (write back) the specified virtual address range.
204 * - start - virtual start address
205 * - end - virtual end address
[all …]
Dcache-v4wt.S104 * - start - virtual start address
105 * - end - virtual end address
117 * - start - virtual start address
118 * - end - virtual end address
147 * Invalidate (discard) the specified virtual address range.
152 * - start - virtual start address
153 * - end - virtual end address
166 * Clean and invalidate the specified virtual address range.
168 * - start - virtual start address
169 * - end - virtual end address
[all …]
Dcache-fa.S109 * - start - virtual start address
110 * - end - virtual end address
122 * - start - virtual start address
123 * - end - virtual end address
161 * Invalidate (discard) the specified virtual address range.
166 * - start - virtual start address
167 * - end - virtual end address
187 * Clean (write back) the specified virtual address range.
189 * - start - virtual start address
190 * - end - virtual end address
[all …]
Dcache-v4.S72 * - start - virtual start address
73 * - end - virtual end address
85 * - start - virtual start address
86 * - end - virtual end address
107 * Clean and invalidate the specified virtual address range.
109 * - start - virtual start address
110 * - end - virtual end address
121 * - start - kernel virtual start address
132 * - start - kernel virtual start address
/kernel/linux/linux-5.10/drivers/usb/usbip/
DKconfig25 This enables the USB/IP virtual host controller driver,
32 int "Number of ports per USB/IP virtual host controller"
37 To increase number of ports available for USB/IP virtual
39 USB/IP virtual host controller.
42 int "Number of USB/IP virtual host controllers"
47 To increase number of ports available for USB/IP virtual
49 virtual host controllers as if adding physical host
66 This enables the USB/IP virtual USB device controller
/kernel/linux/linux-5.10/Documentation/core-api/
Dcachetlb.rst25 virtual-->physical address translations obtained from the software
56 Here we are flushing a specific range of (user) virtual
62 virtual addresses in the range 'start' to 'end-1'.
85 user virtual address 'addr' will be visible to the cpu. That
87 'vma->vm_mm' for virtual address 'addr'.
96 now exists at virtual address "address" for address space
105 is changing an existing virtual-->physical mapping to a new value,
122 a virtual-->physical translation to exist for a virtual address
123 when that virtual address is flushed from the cache. The HyperSparc
129 indexed caches which must be flushed when virtual-->physical
[all …]
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/intel/
Diavf.rst4 Linux Base Driver for Intel(R) Ethernet Adaptive Virtual Function
7 Intel Ethernet Adaptive Virtual Function Linux driver.
25 The iavf driver supports the below mentioned virtual function devices and
36 * Intel(R) XL710 X710 Virtual Function
37 * Intel(R) X722 Virtual Function
38 * Intel(R) XXV710 Virtual Function
39 * Intel(R) Ethernet Adaptive Virtual Function
72 If you have applications that require Virtual Functions (VFs) to receive
87 Adaptive Virtual Function
89 Adaptive Virtual Function (AVF) allows the virtual function driver, or VF, to
[all …]
/kernel/linux/linux-5.10/tools/testing/selftests/kvm/lib/
Dkvm_util.c69 * vm - Virtual Machine
92 * vm - Virtual Machine
254 /* Limit to VA-bit canonical virtual addresses. */ in vm_create()
335 * vm - Virtual Machine
370 * vm - Virtual Machine
399 * vm - Virtual Machine
511 * Memory Compare, host virtual to guest virtual
514 * hva - Starting host virtual address
515 * vm - Virtual Machine
516 * gva - Starting guest virtual address
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/
Ddrm_scatter.c57 vfree(entry->virtual); in drm_sg_cleanup()
120 entry->virtual = vmalloc_32(pages << PAGE_SHIFT); in drm_legacy_sg_alloc()
121 if (!entry->virtual) { in drm_legacy_sg_alloc()
131 memset(entry->virtual, 0, pages << PAGE_SHIFT); in drm_legacy_sg_alloc()
133 entry->handle = ScatterHandle((unsigned long)entry->virtual); in drm_legacy_sg_alloc()
136 DRM_DEBUG("virtual = %p\n", entry->virtual); in drm_legacy_sg_alloc()
138 for (i = (unsigned long)entry->virtual, j = 0; j < pages; in drm_legacy_sg_alloc()
151 /* Verify that each page points to its virtual address, and vice in drm_legacy_sg_alloc()
166 tmp = (unsigned long *)((u8 *) entry->virtual + in drm_legacy_sg_alloc()
175 "virtual mapping\n"); in drm_legacy_sg_alloc()
[all …]
/kernel/linux/linux-5.10/mm/
Dhighmem.c50 * helper functions in its asm/highmem.h to control cache color of virtual
56 * Determine color of virtual address where the page should be mapped.
189 * its virtual address (and hence PTE) without first in flush_all_zero_pkmaps()
271 * Returns the page's virtual memory address.
280 * For highmem pages, we can't trust "virtual" until in kmap_high()
300 * Returns the page's current virtual memory address, or NULL if no mapping
379 * Describes one page->virtual association
383 void *virtual; member
403 * page_address - get the mapped virtual address of a page
404 * @page: &struct page to get the virtual address of
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/
Ddsi-controller.yaml24 can control one to four virtual channels to one panel. Each virtual
25 channel should have a node "panel" for their virtual channel with their
26 reg-property set to the virtual channel number, usually there is just
27 one virtual channel, number 0.
49 The virtual channel number of a DSI peripheral. Must be in the range
51 peripherals respond to more than a single virtual channel. In that
52 case the reg property can take multiple entries, one for each virtual
/kernel/linux/linux-5.10/arch/ia64/include/asm/
Dmca_asm.h30 * This macro converts a instruction virtual address to a physical address
31 * Right now for simulation purposes the virtual addresses are
33 * 1. Lop off bits 61 thru 63 in the virtual address
38 * This macro converts a data virtual address to a physical address
39 * Right now for simulation purposes the virtual addresses are
41 * 1. Lop off bits 61 thru 63 in the virtual address
46 * This macro converts a data physical address to a virtual address
47 * Right now for simulation purposes the virtual addresses are
60 * This macro jumps to the instruction at the given virtual address
75 * 5. Get the physical address corresponding to the virtual address
[all …]
/kernel/linux/linux-5.10/tools/testing/selftests/kvm/include/
Dkvm_util.h26 typedef uint64_t vm_paddr_t; /* Virtual Machine (Guest) physical address */
27 typedef uint64_t vm_vaddr_t; /* Virtual Machine (Guest) virtual address */
29 /* Minimum allocated guest virtual and physical addresses */
91 * vm - Virtual Machine
130 * Address Guest Virtual to Guest Physical
133 * vm - Virtual Machine
134 * gva - VM virtual address
141 * Returns the VM physical address of the translated VM virtual
162 * vm - Virtual Machine
208 * VM Virtual Page Map
[all …]
/kernel/linux/linux-5.10/arch/arm64/mm/
Dcache.S24 * - start - virtual start address of region
25 * - end - virtual end address of region
37 * - start - virtual start address of region
38 * - end - virtual end address of region
77 * - start - virtual start address of region
78 * - end - virtual end address of region
147 * - start - virtual start address of region
186 * - start - virtual start address of region
216 * - start - virtual start address of region
226 * - start - kernel virtual start address
[all …]
/kernel/linux/linux-5.10/drivers/platform/goldfish/
DKconfig3 bool "Platform support for Goldfish virtual devices"
6 Say Y here to get to see options for the Goldfish virtual platform.
14 tristate "Goldfish virtual device for QEMU pipes"
16 This is a virtual device to drive the QEMU pipe interface used by
17 the Goldfish Android Virtual Device.
/kernel/liteos_a/fs/fat/virpart/src/
Dvirpart.c185 * - FR_DENIED : The virtual partition feature has been shut down by switcher
207 * Scan the root directory clean completely, regardless of the virtual partition entry.
238 /* Scan all entry for searching virtual partition directory and others in root directory */ in FatfsScanClear()
265 * Scan virtual partition entry in root directory, and try to rebuild the
266 * error virtual partition, according to the scanning result.
269 * - FR_OCCUPIED : The virtual partition entry has been occupied by the same name file.
270 * - FR_CHAIN_ERR : The virtual partition entry has been rebuilt along the invalid cluster
334 * Bind the virtual partition
337 * - FR_OK : Finished the virtual partition.
338 * The virtual partition result can refer by API
[all …]

12345678910>>...127