Searched full:virtual (Results 1 – 25 of 484) sorted by relevance
12345678910>>...20
| /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 …]
|
| /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
|
| D | mipi-dsi-bus.txt | 26 bus. DSI peripherals are addressed using a 2-bit virtual channel number, so
52 - reg: The virtual channel number of a DSI peripheral. Must be in the range
55 Some DSI peripherals respond to more than a single virtual channel. In that
57 - The reg property can take multiple entries, one for each virtual channel
59 - If the virtual channels that a peripheral responds to are consecutive, the
61 property is the number of the first virtual channel and the second cell is
62 the number of consecutive virtual channels.
88 with different virtual channel configurations.
101 /* peripheral responds to virtual channel 0 */
117 /* peripheral responds to virtual channels 0 and 2 */
[all …]
|
| /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 …]
|
| /Documentation/arch/xtensa/ |
| D | booting.rst | 16 - For configurations with MMUv2 the address must be a virtual address in the
17 default virtual mapping (0xd0000000..0xffffffff).
19 virtual or physical address. In either case it must be within the default
20 virtual mapping. It is considered physical if it is within the range of
22 XCHAL_KSEG_PADDR + XCHAL_KSEG_SIZE), otherwise it is considered virtual.
|
| /Documentation/devicetree/bindings/security/tpm/ |
| D | ibmvtpm.txt | 1 * Device Tree Bindings for IBM Virtual Trusted Platform Module(vtpm)
7 - device_type : specifies type of virtual device
9 sense code associated with this virtual I/O Adapters
18 - ibm,my-dma-window : specifies DMA window associated with this virtual
21 associated with this virtual I/O Adapters
26 Example (IBM Virtual Trusted Platform Module)
|
| /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 …]
|
| /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 …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-memory-tiers | 1 What: /sys/devices/virtual/memory_tiering/
9 /sys/devices/virtual/memory_tiering/memory_tierN/
12 What: /sys/devices/virtual/memory_tiering/memory_tierN/
13 /sys/devices/virtual/memory_tiering/memory_tierN/nodelist
|
| D | sysfs-platform-intel-ifs | 5 What: /sys/devices/virtual/misc/intel_ifs_<N>/run_test
14 /sys/devices/virtual/misc/intel_ifs_<N>/run_test
17 What: /sys/devices/virtual/misc/intel_ifs_<N>/status
25 What: /sys/devices/virtual/misc/intel_ifs_<N>/details
34 What: /sys/devices/virtual/misc/intel_ifs_<N>/image_version
43 What: /sys/devices/virtual/misc/intel_ifs_<N>/current_batch
|
| D | sysfs-firmware-efi-runtime-map | 4 Description: Switching efi runtime services to virtual mode requires
6 bit set to be mapped to virtual addresses.
8 The efi runtime services can only be switched to virtual
10 the same physical to virtual address mappings as the first
32 virt_addr The virtual address of the memory range.
|
| /Documentation/admin-guide/media/ |
| D | misc-cardlist.rst | 17 In order to test userspace applications, there's a number of virtual
24 vicodec Virtual Codec Driver
25 vim2m Virtual Memory-to-Memory Driver
26 vimc Virtual Media Controller Driver (VIMC)
27 vivid Virtual Video Test Driver
|
| /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";
|
| /Documentation/arch/x86/x86_64/ |
| D | 5level-paging.rst | 9 Original x86-64 was limited by 4-level paging to 256 TiB of virtual address
17 It bumps the limits to 128 PiB of virtual address space and 4 PiB of
22 Virtual memory layout for 5-level paging is described in
34 User-space and large virtual address space
36 On x86, 5-level paging enables 56-bit userspace virtual address space.
42 To mitigate this, we are not going to allocate virtual address space
61 about large address space without manually tracking allocated virtual
|
| D | mm.rst | 7 Complete virtual memory map with 4-level page tables
32 …0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory, different …
36 … | | | | virtual memory addresses up to the -128 TB
40 … | Kernel-space virtual memory, shared between all processes:
49 ffffea0000000000 | -22 TB | ffffeaffffffffff | 1 TB | virtual memory map (vmemmap_base)
75 Complete virtual memory map with 5-level page tables
91 …0000000000000000 | 0 | 00ffffffffffffff | 64 PB | user-space virtual memory, different …
95 … | | | | virtual memory addresses up to the -64 PB
99 … | Kernel-space virtual memory, shared between all processes:
108 ffd4000000000000 | -11 PB | ffd5ffffffffffff | 0.5 PB | virtual memory map (vmemmap_base)
[all …]
|
| /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 …]
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 9 GenieZone hypervisor (gzvm) is a type-1 hypervisor that supports various virtual
38 - Virtual Platform
40 We manage to emulate a virtual mobile platform for guest OS running on guest
42 virtual arch timer, GIC, MMIO, PSCI, and exception watching...etc.
52 redirect MMIO traps back to VMM where the virtual devices are mostly emulated.
59 hypervisor with the help of gzvm module, both virtual and physical ones.
85 we intend to support all SPI, PPI, and SGI. When it comes to virtual
|
| /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 …]
|
| /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 …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | intel,ce4100-lapic.yaml | 42 intel,virtual-wire-mode:
47 Virtual Wire Mode - use lapic as virtual wire interrupt delivery mode.
52 mode is configured to virtual wire compatibility mode.
70 intel,virtual-wire-mode;
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | xen,shared-memory.txt | 4 virtual machine. Typically, a region is configured at VM creation time
5 to be a shared memory area across multiple virtual machines for
19 64 bit integer offset within the owner virtual machine's shared
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | firmware.txt | 16 - virtual-traps: The virtual traps, taken from the firmware binary.
23 virtual-traps = <0 0 0 0 0 0 0 0>;
|
| /Documentation/devicetree/bindings/firmware/ |
| D | mediatek,geniezone.yaml | 15 Execution Environment) and AVF (Android Virtualization Framework) virtual
18 exposes hypervisor control interfaces to the VMM for managing virtual
19 machine lifecycles and assisting virtual device emulation.
|
| /Documentation/mm/ |
| D | page_tables.rst | 7 Paged virtual memory was invented along with virtual memory as a concept in
9 virtual memory. The feature migrated to newer computers and became a de facto
13 Page tables map virtual addresses as seen by the CPU into physical addresses
20 The physical address corresponding to the virtual address is often referenced
50 would be very sparse, because large portions of the virtual memory usually
51 remains unused. By using hierarchical page tables large holes in the virtual
58 shortcuts in mapping virtual memory to physical memory: there is no need to
89 mapping a single page of virtual memory to a single page of physical memory.
152 virtual memory manager, will need to be written so that it traverses all of the
|
| /Documentation/riscv/ |
| D | vm-layout.rst | 4 Virtual Memory Layout on RISC-V Linux
10 This document describes the virtual memory layout used by the RISC-V Linux
26 occur.": that splits the virtual address space into 2 halves separated by a very
39 …0000000000000000 | 0 | 0000003fffffffff | 256 GB | user-space virtual memory, different …
43 … | | | | virtual memory addresses up to the -256 GB
47 … | Kernel-space virtual memory, shared between all processes:
75 …0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory, different …
79 … | | | | virtual memory addresses up to the -128 TB
83 … | Kernel-space virtual memory, shared between all processes:
111 …0000000000000000 | 0 | 00ffffffffffffff | 64 PB | user-space virtual memory, different …
[all …]
|
12345678910>>...20