| /kernel/linux/linux-6.6/net/vmw_vsock/ |
| D | Kconfig | 7 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/net/vmw_vsock/ |
| D | Kconfig | 7 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/ |
| D | overview.txt | 19 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-6.6/arch/arm/mach-omap2/ |
| D | io.c | 67 .virtual = L3_24XX_VIRT,
73 .virtual = L4_24XX_VIRT,
83 .virtual = DSP_MEM_2420_VIRT,
89 .virtual = DSP_IPI_2420_VIRT,
95 .virtual = DSP_MMU_2420_VIRT,
107 .virtual = L4_WK_243X_VIRT,
113 .virtual = OMAP243X_GPMC_VIRT,
119 .virtual = OMAP243X_SDRC_VIRT,
125 .virtual = OMAP243X_SMS_VIRT,
137 .virtual = L3_34XX_VIRT,
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| D | io.c | 70 .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-6.6/arch/arm64/mm/ |
| D | cache.S | 24 * - start - virtual start address of region
25 * - end - virtual end address of region
52 * - start - virtual start address of region
53 * - end - virtual end address of region
68 * - start - virtual start address of region
69 * - end - virtual end address of region
89 * - start - virtual start address of region
90 * - end - virtual end address of region
108 * - start - virtual start address of region
109 * - end - virtual end address of region
[all …]
|
| /kernel/linux/linux-5.10/Documentation/sparc/oradax/ |
| D | dax-hv-api.txt | 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 …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-6.6/Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 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 …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-6.6/drivers/gpu/drm/i915/gvt/ |
| D | vgpu.c | 161 * intel_gvt_activate_vgpu - activate a virtual GPU
162 * @vgpu: virtual GPU
164 * This function is called when user wants to activate a virtual GPU.
173 * intel_gvt_deactivate_vgpu - deactivate a virtual GPU
174 * @vgpu: virtual GPU
176 * This function is called when user wants to deactivate a virtual GPU.
177 * The virtual GPU will be stopped.
198 * intel_gvt_release_vgpu - release a virtual GPU
199 * @vgpu: virtual GPU
201 * This function is called when user wants to release a virtual GPU.
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/gvt/ |
| D | vgpu.c | 208 * 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-6.6/Documentation/networking/ |
| D | representors.rst | 23 virtual switches and IOV devices. Just as each physical port of a Linux-
24 controlled switch has a separate netdev, so does each virtual port of a virtual
27 the virtual functions appear in the networking stack of the PF via the
28 representors. The PF can thus always communicate freely with the virtual
34 administrative commands) and a data plane object (one end of a virtual pipe).
35 As a virtual link endpoint, the representor can be configured like any other
44 which has administrative control over the virtual switch on the device.
48 for the whole device or might have a separate virtual switch, and hence
68 fast-path rules in the virtual switch. Packets transmitted on the
71 be received on the representor netdevice. (That is, there is a virtual pipe
[all …]
|
| /kernel/linux/linux-5.10/drivers/misc/habanalabs/common/ |
| D | memory.c | 20 * 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/ |
| D | sva.rst | 4 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-6.6/sound/isa/wavefront/ |
| D | wavefront_midi.c | 14 * "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/sound/isa/wavefront/ |
| D | wavefront_midi.c | 14 * "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-6.6/Documentation/core-api/ |
| D | cachetlb.rst | 25 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'.
98 at virtual address "address" for "nr" consecutive pages.
109 is changing an existing virtual-->physical mapping to a new value,
126 a virtual-->physical translation to exist for a virtual address
127 when that virtual address is flushed from the cache. The HyperSparc
133 indexed caches which must be flushed when virtual-->physical
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | porting.rst | 12 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-6.6/Documentation/arch/arm/ |
| D | porting.rst | 12 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-6.6/arch/arm/mm/ |
| D | cache-v4wb.S | 145 * - start - virtual start address
146 * - end - virtual end address
158 * - start - virtual start address
159 * - end - virtual end address
177 * Invalidate (discard) the specified virtual address range.
182 * - start - virtual start address
183 * - end - virtual end address
201 * Clean (write back) the specified virtual address range.
203 * - start - virtual start address
204 * - end - virtual end address
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mm/ |
| D | cache-v4wb.S | 146 * - 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 …]
|
| /kernel/linux/linux-5.10/drivers/usb/usbip/ |
| D | Kconfig | 25 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-6.6/drivers/usb/usbip/ |
| D | Kconfig | 25 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-6.6/Documentation/networking/device_drivers/ethernet/intel/ |
| D | iavf.rst | 4 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/Documentation/core-api/ |
| D | cachetlb.rst | 25 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/ |
| D | iavf.rst | 4 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 …]
|