| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …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
[all …]
|
| /linux-6.12.1/drivers/gpu/drm/i915/gvt/ |
| D | vgpu.c | 162 * intel_gvt_activate_vgpu - activate a virtual GPU
163 * @vgpu: virtual GPU
165 * This function is called when user wants to activate a virtual GPU.
174 * intel_gvt_deactivate_vgpu - deactivate a virtual GPU
175 * @vgpu: virtual GPU
177 * This function is called when user wants to deactivate a virtual GPU.
178 * The virtual GPU will be stopped.
199 * intel_gvt_release_vgpu - release a virtual GPU
200 * @vgpu: virtual GPU
202 * This function is called when user wants to release a virtual GPU.
[all …]
|
| /linux-6.12.1/Documentation/networking/ |
| D | representors.rst | 24 virtual switches and IOV devices. Just as each physical port of a Linux-
25 controlled switch has a separate netdev, so does each virtual port of a virtual
28 the virtual functions appear in the networking stack of the PF via the
29 representors. The PF can thus always communicate freely with the virtual
35 administrative commands) and a data plane object (one end of a virtual pipe).
36 As a virtual link endpoint, the representor can be configured like any other
45 which has administrative control over the virtual switch on the device.
49 for the whole device or might have a separate virtual switch, and hence
69 fast-path rules in the virtual switch. Packets transmitted on the
72 be received on the representor netdevice. (That is, there is a virtual pipe
[all …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/arch/arm/mm/ |
| D | cache-v4wb.S | 151 * - start - virtual start address
152 * - end - virtual end address
167 * - start - virtual start address
168 * - end - virtual end address
186 * Invalidate (discard) the specified virtual address range.
191 * - start - virtual start address
192 * - end - virtual end address
210 * Clean (write back) the specified virtual address range.
212 * - start - virtual start address
213 * - end - virtual end address
[all …]
|
| D | cache-v4wt.S | 107 * - start - virtual start address
108 * - end - virtual end address
123 * - start - virtual start address
124 * - end - virtual end address
155 * Invalidate (discard) the specified virtual address range.
160 * - start - virtual start address
161 * - end - virtual end address
174 * Clean and invalidate the specified virtual address range.
176 * - start - virtual start address
177 * - end - virtual end address
[all …]
|
| D | cache-fa.S | 111 * - start - virtual start address
112 * - end - virtual end address
127 * - start - virtual start address
128 * - end - virtual end address
168 * Invalidate (discard) the specified virtual address range.
173 * - start - virtual start address
174 * - end - virtual end address
194 * Clean (write back) the specified virtual address range.
196 * - start - virtual start address
197 * - end - virtual end address
[all …]
|
| D | cache-v4.S | 75 * - start - virtual start address
76 * - end - virtual end address
89 * - start - virtual start address
90 * - end - virtual end address
115 * Clean and invalidate the specified virtual address range.
117 * - start - virtual start address
118 * - end - virtual end address
130 * - start - kernel virtual start address
142 * - start - kernel virtual start address
|
| D | cache-v6.S | 113 * - start - virtual start address of region
114 * - end - virtual end address of region
132 * - start - virtual start address of region
133 * - end - virtual end address of region
162 * Fault handling for the cache operation above. If the virtual address in r0
206 * - start - virtual start address of region
207 * - end - virtual end address of region
239 * - start - virtual start address of region
240 * - end - virtual end address of region
259 * - start - virtual start address of region
[all …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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
|
| /linux-6.12.1/Documentation/arch/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 …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/display/ |
| D | dsi-controller.yaml | 24 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.
58 The virtual channel number of a DSI peripheral. Must be in the range
60 peripherals respond to more than a single virtual channel. In that
61 case the reg property can take multiple entries, one for each virtual
|
| /linux-6.12.1/drivers/accel/habanalabs/common/ |
| D | memory.c | 56 * device virtual memory.
60 * virtual range which is a half of the total device virtual range.
62 * On each mapping of physical pages, a suitable virtual range chunk (with a
67 * On each Unmapping of a virtual address, the relevant virtual chunk is
73 * virtual range (which is a half of the device total virtual range).
214 * dma_map_host_va() - DMA mapping of the given host virtual address.
216 * @addr: the host virtual address of the memory area.
265 * dma_unmap_host_va() - DMA unmapping of the given host virtual address.
389 * clear_va_list_locked() - free virtual addresses list.
391 * @va_list: list of virtual addresses to free.
[all …]
|
| /linux-6.12.1/Documentation/admin-guide/mm/ |
| D | concepts.rst | 11 here we assume that an MMU is available and a CPU can translate a virtual
16 Virtual Memory Primer
28 to avoid this complexity a concept of virtual memory was developed.
30 The virtual memory abstracts the details of physical memory from the
35 With virtual memory, each and every memory access uses a virtual
37 writes) from (or to) the system memory, it translates the `virtual`
47 Each physical memory page can be mapped as one or more virtual
49 translation from a virtual address used by programs to the physical
58 virtual address are used to index an entry in the top level page
60 hierarchy with the next bits of the virtual address as the index to
[all …]
|
| /linux-6.12.1/tools/testing/selftests/kvm/include/aarch64/ |
| D | arch_timer.h | 12 VIRTUAL, enumerator
39 case VIRTUAL: in timer_get_cntct()
54 case VIRTUAL: in timer_set_cval()
70 case VIRTUAL: in timer_get_cval()
85 case VIRTUAL: in timer_set_tval()
102 case VIRTUAL: in timer_get_tval()
117 case VIRTUAL: in timer_set_ctl()
133 case VIRTUAL: in timer_get_ctl()
|
| /linux-6.12.1/drivers/tty/ |
| D | Kconfig | 14 bool "Virtual terminal" if EXPERT
19 display and keyboard devices. These are called "virtual" because you
20 can run several virtual terminals (also called virtual consoles) on
22 virtual terminal can collect system messages and warnings, another
24 an X session, all in parallel. Switching between virtual terminals
28 properties (such as colors or beeping) of a virtual terminal. The
31 directly. The fonts used on virtual terminals can be changed with
35 You need at least one virtual terminal device in order to make use
50 on virtual consoles.
53 bool "Support for console on virtual terminal" if EXPERT
[all …]
|
| /linux-6.12.1/drivers/dma/ |
| D | virt-dma.h | 3 * Virtual DMA channel support for DMAengine
52 * @vc: virtual channel allocating this descriptor
53 * @vd: virtual descriptor to prepare
78 * @vc: virtual channel to update
92 * @vd: virtual descriptor to update
114 * @vd: virtual descriptor to free/reuse
133 * @vd: virtual descriptor
145 * @vd: virtual descriptor to be terminated
163 * @vc: virtual channel to obtain descriptor from
177 * @vc: virtual channel to get descriptors from
[all …]
|
| /linux-6.12.1/drivers/platform/goldfish/ |
| D | Kconfig | 3 bool "Platform support for Goldfish virtual devices"
7 Say Y here to get to see options for the Goldfish virtual platform.
15 tristate "Goldfish virtual device for QEMU pipes"
17 This is a virtual device to drive the QEMU pipe interface used by
18 the Goldfish Android Virtual Device.
|
| /linux-6.12.1/Documentation/devicetree/bindings/usb/ |
| D | aspeed,usb-vhub.yaml | 8 title: ASPEED USB 2.0 Virtual Hub Controller
14 The ASPEED USB 2.0 Virtual Hub Controller implements 1 set of USB Hub
16 the Virtual Hub's downstream USB devices.
19 revisions. AST2400 and AST2500 Virtual Hub supports 5 downstream devices
20 and 15 generic endpoints, while AST2600 Virtual Hub supports 7 downstream
40 description: Number of downstream ports supported by the Virtual Hub
47 description: Number of generic endpoints supported by the Virtual Hub
135 product = "USB Virtual Hub";
|