Searched full:virtual (Results 1 – 25 of 379) sorted by relevance
12345678910>>...16
| /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 …]
|
| /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.
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
|
| 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/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/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/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/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
133 product = "USB Virtual Hub";
|
| /Documentation/x86/x86_64/ |
| D | 5level-paging.rst | 9 Original x86-64 was limited by 4-level paing 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/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 …]
|
| /Documentation/ABI/testing/ |
| 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/mm/ |
| D | concepts.rst | 13 here we assume that an MMU is available and a CPU can translate a virtual
18 Virtual Memory Primer
30 to avoid this complexity a concept of virtual memory was developed.
32 The virtual memory abstracts the details of physical memory from the
37 With virtual memory, each and every memory access uses a virtual
39 writes) from (or to) the system memory, it translates the `virtual`
49 Each physical memory page can be mapped as one or more virtual
51 translation from a virtual address used by programs to the physical
60 virtual address are used to index an entry in the top level page
62 hierarchy with the next bits of the virtual address as the index to
[all …]
|
| D | userfaultfd.rst | 22 The ``userfaultfd`` (aside from registering and unregistering virtual
28 2) various ``UFFDIO_*`` ioctls that can manage the virtual memory regions
30 resolve the userfaults it receives via 1) or to manage the virtual
33 The real advantage of userfaults if compared to regular virtual memory
39 when dealing with virtual address spaces that could span
76 etc) virtual memory areas, respectively.
79 ``UFFDIO_REGISTER_MODE_MINOR`` registration for hugetlbfs virtual memory
81 support for shmem virtual memory areas.
98 Userland can use the ``uffdio_register.ioctls`` to manage the virtual
194 externalization consisting of a virtual machine running with part or
[all …]
|
| /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/admin-guide/ |
| D | serial-console.rst | 22 device: tty0 for the foreground virtual console
23 ttyX for any other virtual console
42 virtual console, and kernel messages will appear on both the VGA
62 1. Create ``/dev/console`` (real console) and ``/dev/tty0`` (master virtual
92 set the baudrate to 38400 (baudrate of the virtual console).
95 Programs that want to do something with the virtual console usually
97 and your console is NOT the virtual console some programs will fail.
|
| /Documentation/infiniband/ |
| D | opa_vnic.rst | 2 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC)
5 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC) feature
12 involves one or more virtual Ethernet switches overlaid on the Omni-Path
15 virtual Ethernet switch. The virtual Ethernet switches are logical
19 single virtual Ethernet switch. A virtual Ethernet switch, is effectively
23 different virtual Ethernet switch. The below diagram presents a case
24 of two virtual Ethernet switches with two HFI nodes::
36 | Virtual Ethernet Switch | | Virtual Ethernet Switch |
97 The L4 header field contains the virtual Ethernet switch id the VNIC port
|
| /Documentation/powerpc/ |
| D | cxlflash.rst | 19 devices as a PCI device by implementing a virtual PCI host bridge.
48 partition of the LUN (referred to as virtual LUN access). The
49 segmentation of a disk device into virtual LUNs is assisted
96 The first mode is called a virtual mode. In this mode a single scsi
98 virtual LUNs. The virtual LUNs may be resized as long as the sum of
99 the sizes of all the virtual LUNs, along with the meta-data associated
108 restart and also reboot. The virtual LUNs do not persist (i.e. do
222 This ioctl is responsible for transitioning the LUN to virtual mode
223 of access and configuring the AFU for virtual access from user space
232 The AFU is configured for virtual access from user space by adding
[all …]
|
| /Documentation/arm64/ |
| D | tagged-pointers.rst | 2 Tagged virtual addresses in AArch64 Linux
9 This document briefly describes the provision of tagged virtual
15 the virtual address ignored by the translation hardware. This frees up
60 on the tag information for user virtual addresses being maintained
87 likely that C compilers will not hazard two virtual addresses differing
|
| /Documentation/devicetree/bindings/dma/ |
| D | fsl-qdma.txt | 24 - block-number: the virtual block number
25 - block-offset: the offset of different virtual block
26 - status-sizes: status queue size of per virtual block
27 - queue-sizes: command queue size of per virtual block, the size number
|
| /Documentation/hwmon/ |
| D | pmbus-core.rst | 67 standard PMBus commands and virtual PMBus commands.
75 Virtual PMBus commands
78 Virtual PMBus commands are provided to enable support for non-standard
82 Virtual PMBus commands start with command value 0x100 and can thus easily be
84 than 0xff). Support for virtual PMBus commands is device specific and thus has
87 Virtual commands are named PMBUS_VIRT_xxx and start with PMBUS_VIRT_BASE. All
88 virtual commands are word sized.
90 There are currently two types of virtual commands.
97 Virtual commands have to be handled in device specific driver code. Chip driver
98 code returns non-negative values if a virtual command is supported, or a
[all …]
|
| /Documentation/admin-guide/kdump/ |
| D | vmcoreinfo.rst | 53 virtual to physical addresses.
59 the kernel start address. Used to convert a virtual address from the
65 Stores the virtual area list. makedumpfile gets the vmalloc start value
152 virtual address for memory map.
347 Used to convert the virtual address of an exported kernel symbol to its
353 Used to walk through the whole page table and convert virtual addresses
383 Currently unused by Makedumpfile. Used to compute the module virtual
414 crash kernel when converting virtual addresses to physical addresses.
452 The maximum number of bits for virtual addresses. Used to compute the
453 virtual memory ranges.
[all …]
|
12345678910>>...16