Searched full:mappings (Results 1 – 25 of 153) sorted by relevance
1234567
| /Documentation/mm/ |
| D | highmem.rst | 15 at all times. This means the kernel needs to start using temporary mappings of
48 Temporary Virtual Mappings
51 The kernel contains several ways of creating temporary mappings. The following
55 short term mappings. They can be invoked from any context (including
56 interrupts) but the mappings can only be used in the context which acquired
64 These mappings are thread-local and CPU-local, meaning that the mapping
89 mappings, the local mappings are only valid in the context of the caller
94 Most code can be designed to use thread local mappings. User should
99 Nesting kmap_local_page() and kmap_atomic() mappings is allowed to a certain
103 mappings.
[all …]
|
| D | hugetlbfs_reserv.rst | 87 of mappings. Location differences are:
89 - For private mappings, the reservation map hangs off the VMA structure.
92 - For shared mappings, the reservation map hangs off the inode. Specifically,
93 inode->i_mapping->private_data. Since shared mappings are always backed
121 One of the big differences between PRIVATE and SHARED mappings is the way
124 - For shared mappings, an entry in the reservation map indicates a reservation
127 - For private mappings, the lack of an entry in the reservation map indicates
133 For private mappings, hugetlb_reserve_pages() creates the reservation map and
138 are needed for the current mapping/segment. For private mappings, this is
139 always the value (to - from). However, for shared mappings it is possible that
[all …]
|
| D | ksm.rst | 41 if compared to an unlimited list of reverse mappings. It is still
48 (i.e. virtual mappings) that are sharing the page, which is in turn
|
| /Documentation/arch/arm/ |
| D | memory.rst | 62 Machine specific static mappings are also
72 PKMAP_BASE PAGE_OFFSET-1 Permanent kernel mappings
78 placed here using dynamic mappings.
85 00001000 TASK_SIZE-1 User space mappings
86 Per-thread mappings are placed here via
96 Please note that mappings which collide with the above areas may result
103 must set up their own mappings using open() and mmap().
|
| D | porting.rst | 67 address PHYS_OFFSET, along with any other mappings you supply.
83 (In other words, you can't put IO mappings below TASK_SIZE, and
98 any static mappings in this area; vmalloc will overwrite them.
|
| /Documentation/driver-api/ |
| D | io-mapping.rst | 44 used with mappings created by io_mapping_create_wc()
46 Temporary mappings are only valid in the context of the caller. The mapping
56 Nested mappings need to be undone in reverse order because the mapping
65 The mappings are released with::
83 The mappings are released with::
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 29 These behave very much like private mappings, except that they're
133 In the no-MMU case, however, anonymous mappings are backed by physical
147 (#) A list of all the private copy and anonymous mappings on the system is
150 (#) A list of all the mappings in use by a process is visible through
176 mappings made by a process or if the mapping in which the address lies does not
191 Shared mappings may not be moved. Shareable mappings may not be moved either,
196 mappings, move parts of existing mappings or resize parts of mappings. It must
243 mappings may still be mapped directly off the device under some
250 Provision of shared mappings on memory backed files is similar to the provision
253 of pages and permit mappings to be made on that.
[all …]
|
| D | concepts.rst | 48 pages. These mappings are described by page tables that allow
93 manages such mappings transparently to the user and hence the
143 The `anonymous memory` or `anonymous mappings` represent memory that
144 is not backed by a filesystem. Such mappings are implicitly created
146 call. Usually, the anonymous mappings only define virtual memory areas
|
| /Documentation/driver-api/usb/ |
| D | dma.rst | 19 manage dma mappings for existing dma-ready buffers (see below).
27 don't manage dma mappings for URBs.
41 IOMMU to manage the DMA mappings. It can cost MUCH more to set up and
42 tear down the IOMMU mappings with each request than perform the I/O!
64 "streaming" DMA mappings.)
|
| /Documentation/devicetree/bindings/iommu/ |
| D | xen,grant-dma.yaml | 13 The Xen IOMMU represents the Xen grant table interface. Grant mappings
16 The binding is required to restrict memory access using Xen grant mappings.
|
| /Documentation/filesystems/iomap/ |
| D | design.rst | 24 This layer tries to obtain mappings of each file ranges to storage
28 2. An upper layer that acts upon the space mappings provided by the
31 The iteration can involve mappings of file's logical offset ranges to
62 units (generally memory pages or blocks) and looks up space mappings on
64 largest space mappings that it can create for a given file operation and
69 Larger space mappings improve runtime performance by amortizing the cost
238 * **IOMAP_F_MERGED**: Multiple contiguous block mappings were
272 ``IOMAP_INLINE`` mappings.
282 that should be used to detect stale mappings.
286 Filesystems with completely static mappings need not set this value.
[all …]
|
| D | operations.rst | 295 though it will `reuse mappings
298 Do not return ``IOMAP_INLINE`` mappings here; the ``->iomap_end``
300 Do not return ``IOMAP_DELALLOC`` mappings here; iomap currently
303 mappings have not changed.
542 extent mappings, handle write failures, etc.
549 copy on write operation, so the ioend should switch mappings.
653 For unwritten mappings, the pagecache will be searched.
668 For unwritten mappings, the pagecache will be searched.
683 All mappings must be mapped or unwritten; cannot be dirty or shared, and
696 The ``iomap_fiemap`` function exports file extent mappings to userspace
|
| /Documentation/devicetree/bindings/ |
| D | .yamllint | 36 forbid-in-block-mappings: true
37 forbid-in-flow-mappings: true
|
| /Documentation/gpu/rfc/ |
| D | i915_vm_bind.h | 17 * 1: In VM_UNBIND calls, the UMD must specify the exact mappings created
19 * mappings or splitting them. Similarly, VM_BIND calls will not replace
20 * any existing mappings.
22 * 2: The restrictions on unbinding partial or multiple mappings is
23 * lifted, Similarly, binding will replace any mappings in the given range.
93 * Multiple VA mappings can be created to the same section of the object
|
| D | i915_vm_bind.rst | 9 specified address space (VM). These mappings (also referred to as persistent
10 mappings) will be persistent across multiple GPU submissions (execbuf calls)
12 mappings during each submission (as required by older execbuf mode).
27 * Multiple Virtual Address (VA) mappings can map to the same physical pages
30 * Support capture of persistent mappings in the dump upon GPU error.
90 path (where required mappings are already bound) submission latency is O(1)
201 execbuf. VM_BIND allows bind/unbind of mappings required for the directly
231 mapped objects. Page table pages are similar to persistent mappings of a
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-efi-runtime-map | 10 the same physical to virtual address mappings as the first
11 kernel. The mappings are exported to sysfs so userspace tools
|
| /Documentation/arch/arm64/ |
| D | hugetlbpage.rst | 15 1) Block mappings at the pud/pmd level
20 mappings reduce the depth of page table walk needed to translate hugepage
|
| D | memory.rst | 22 swapper_pg_dir contains only kernel (global) mappings while the user pgd
23 contains only user (non-global) mappings. The swapper_pg_dir address is
36 fffffbfff0000000 fffffbfffdffffff 224MB fixed mappings (top down)
53 fffffbfff0000000 fffffbfffdffffff 224MB fixed mappings (top down)
99 mappings are created, since the host kernel runs directly in EL2.
|
| /Documentation/core-api/ |
| D | dma-api-howto.rst | 35 mappings between physical and bus addresses.
172 The setup for streaming mappings is performed via a call to
234 coherent allocations, but supports full 64-bits for streaming mappings
257 kernel will use this information later when you make DMA mappings.
296 Types of DMA mappings
299 There are two types of DMA mappings:
301 - Consistent DMA mappings which are usually mapped at driver
314 Good examples of what to use consistent mappings for are:
323 versa. Consistent mappings guarantee this.
345 - Streaming DMA mappings which are usually mapped for one DMA
[all …]
|
| /Documentation/netlabel/ |
| D | cipso_ipv4.rst | 46 appropriate for the host. These mappings are defined as part of a CIPSO
55 mappings from the network labels to the corresponding LSM identifiers. The
|
| /Documentation/userspace-api/media/drivers/ |
| D | uvcvideo.rst | 23 - through mappings of XU controls to V4L2 controls
37 Control mappings
41 control mappings at runtime. These allow for individual XU controls or byte
47 The ioctl used to create these control mappings is called UVCIOC_CTRL_MAP.
117 control and a V4L2 control. Once mappings are defined, userspace
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-table-change.rst | 6 Changing default Remote Controller mappings
|
| /Documentation/core-api/irq/ |
| D | irq-domain.rst | 50 In most cases, the irq_domain will begin empty without any mappings
51 between hwirq and IRQ numbers. Mappings are added to the irq_domain
82 Types of irq_domain mappings
187 The legacy map should only be used if fixed IRQ mappings must be
192 Most users of legacy mappings should use irq_domain_add_simple() or
|
| /Documentation/driver-api/gpio/ |
| D | board.rst | 2 GPIO Mappings
10 describe its hardware layout. Currently, mappings can be defined through device
19 GPIOs mappings are defined in the consumer device's node, in a property named
105 gpiod_lookup structure. Two macros are defined to help declaring such mappings::
|
| /Documentation/arch/x86/ |
| D | pti.rst | 51 For new userspace mappings, the kernel makes the entries in its
103 process. Even without PTI, the shared kernel mappings
106 mappings: one in the kernel page tables that maps everything
168 in the mappings cause these.
|
1234567