Home
last modified time | relevance | path

Searched full:mappings (Results 1 – 25 of 1019) sorted by relevance

12345678910>>...41

/linux/Documentation/mm/
H A Dhighmem.rst15 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 …]
/linux/drivers/gpu/drm/nouveau/
H A Dnouveau_exec.c27 * and unmap memory. Mappings may be flagged as sparse. Sparse mappings are not
31 * Userspace may request memory backed mappings either within or outside of the
33 * mapping. Subsequently requested memory backed mappings within a sparse
35 * mapping. If such memory backed mappings are unmapped the kernel will make
37 * Requests to unmap a sparse mapping that still contains memory backed mappings
38 * will result in those memory backed mappings being unmapped first.
40 * Unmap requests are not bound to the range of existing mappings and can even
41 * overlap the bounds of sparse mappings. For such a request the kernel will
42 * make sure to unmap all memory backed mappings within the given range,
43 * splitting up memory backed mappings which are only partially contained
[all …]
/linux/arch/x86/include/asm/
H A Dinvpcid.h13 * mappings, we don't want the compiler to reorder any subsequent in __invpcid()
25 /* Flush all mappings for a given pcid and addr, not including globals. */
32 /* Flush all mappings for a given PCID, not including globals. */
38 /* Flush all mappings, including globals, for all PCIDs. */
44 /* Flush all mappings for all PCIDs except globals. */
/linux/Documentation/arch/arm/
H A Dmemory.rst62 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().
/linux/tools/testing/selftests/kvm/
H A Dkvm_page_table_test.c110 * Then KVM will create normal page mappings or huge block in guest_code()
111 * mappings for them. in guest_code()
126 * normal page mappings from RO to RW if memory backing src type in guest_code()
128 * mappings into normal page mappings if memory backing src type in guest_code()
150 * this will create new mappings at the smallest in guest_code()
164 * split page mappings back to block mappings. And a TLB in guest_code()
166 * page mappings are not fully invalidated. in guest_code()
362 /* Test the stage of KVM creating mappings */ in run_test()
372 /* Test the stage of KVM updating mappings */ in run_test()
385 /* Test the stage of KVM adjusting mappings */ in run_test()
/linux/arch/sh/mm/
H A Dpmb.c50 /* Adjacent entry link for contiguous multi-entry mappings */
172 * Finally for sizes that involve compound mappings, walk in pmb_mapping_exists()
424 * Small mappings need to go through the TLB. in pmb_remap_caller()
530 pr_info("PMB: boot mappings:\n"); in pmb_notify()
551 * Sync our software copy of the PMB mappings with those in hardware. The
552 * mappings in the hardware PMB were either set up by the bootloader or
561 * Run through the initial boot mappings, log the established in pmb_synchronize()
563 * PPN range. Specifically, we only care about existing mappings in pmb_synchronize()
567 * loader can establish multi-page mappings with the same caching in pmb_synchronize()
573 * jumping between the cached and uncached mappings and tearing in pmb_synchronize()
[all …]
/linux/Documentation/driver-api/
H A Dio-mapping.rst44 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::
/linux/Documentation/filesystems/iomap/
H A Ddesign.rst24 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
237 * **IOMAP_F_MERGED**: Multiple contiguous block mappings were
287 ``IOMAP_INLINE`` mappings.
295 that should be used to detect stale mappings.
299 Filesystems with completely static mappings need not set this value.
[all …]
/linux/drivers/gpu/drm/tegra/
H A Dsubmit.c150 xa_lock(&context->mappings); in tegra_drm_mapping_get()
152 mapping = xa_load(&context->mappings, id); in tegra_drm_mapping_get()
156 xa_unlock(&context->mappings); in tegra_drm_mapping_get()
261 struct tegra_drm_used_mapping *mappings; in submit_process_bufs() local
273 mappings = kzalloc_objs(*mappings, args->num_bufs); in submit_process_bufs()
274 if (!mappings) { in submit_process_bufs()
303 mappings[i].mapping = mapping; in submit_process_bufs()
304 mappings[i].flags = buf->flags; in submit_process_bufs()
307 job_data->used_mappings = mappings; in submit_process_bufs()
316 tegra_drm_mapping_put(mappings[i].mapping); in submit_process_bufs()
[all …]
/linux/arch/hexagon/include/asm/
H A Dmem-layout.h71 * Permanent IO mappings will live at 0xfexx_xxxx
80 * "permanent kernel mappings", defined as long-lasting mappings of
92 * "Permanent Kernel Mappings"; fancy (or less fancy) PTE table
/linux/Documentation/userspace-api/
H A Dmseal.rst133 - System mappings:
134 The system mappings are created by the kernel and includes vdso, vvar,
137 Those system mappings are readonly only or execute only, memory sealing can
143 the CONFIG_MSEAL_SYSTEM_MAPPINGS seals all system mappings of this
150 or unmapping system mappings. Known broken software at the time
174 the heap manager's ability to manage the mappings; the outcome is
188 attributes, such as protection bits (RWX). Sealed mappings doesn't mean the
/linux/Documentation/driver-api/usb/
H A Ddma.rst19 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.)
/linux/drivers/soc/aspeed/
H A DKconfig13 Control LPC firmware cycle mappings through ioctl()s. The driver
43 Control ASPEED P2A VGA MMIO to BMC mappings through ioctl()s. The
44 driver also provides an interface for userspace mappings to a
/linux/Documentation/gpu/rfc/
H A Di915_vm_bind.rst9 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
H A Di915_vm_bind.h17 * 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
/linux/include/drm/
H A Ddrm_cache.h56 * for some buffers, both the CPU and the GPU use uncached mappings, in drm_arch_can_wc_memory()
59 * The use of uncached GPU mappings relies on the correct implementation in drm_arch_can_wc_memory()
61 * will use cached mappings nonetheless. On x86 platforms, this does not in drm_arch_can_wc_memory()
62 * seem to matter, as uncached CPU mappings will snoop the caches in any in drm_arch_can_wc_memory()
/linux/drivers/iommu/
H A Dvirtio-iommu.c70 struct rb_root_cached mappings; member
346 interval_tree_insert(&mapping->iova, &vdomain->mappings); in viommu_add_mapping()
353 * viommu_del_mappings - remove mappings from the internal tree
370 next = interval_tree_iter_first(&vdomain->mappings, iova, end); in viommu_del_mappings()
386 interval_tree_remove(node, &vdomain->mappings); in viommu_del_mappings()
395 * Fill the domain with identity mappings, skipping the device's reserved
447 * mappings were deleted from the device. Re-create the mappings available in
459 node = interval_tree_iter_first(&vdomain->mappings, 0, -1UL); in viommu_replay_mappings()
678 vdomain->mappings = RB_ROOT_CACHED; in viommu_domain_alloc_paging()
702 /* Free all remaining mappings */ in viommu_domain_free()
[all …]
H A Dmsm_iommu.h12 /* Sharability attributes of MSM IOMMU mappings */
16 /* Cacheability attributes of MSM IOMMU mappings */
28 * be present. These mappings are typically determined at design time and are
/linux/tools/testing/selftests/namespaces/
H A Dfile_handle_test.c480 /* Write uid/gid mappings to maintain some capabilities */ in TEST()
486 write(pipefd[1], "M", 1); /* Unable to set mappings */ in TEST()
547 return, "Cannot set uid/gid mappings"); in TEST()
609 /* Write uid/gid mappings to maintain some capabilities */ in TEST()
615 write(pipefd[1], "M", 1); /* Unable to set mappings */ in TEST()
676 return, "Cannot set uid/gid mappings"); in TEST()
738 /* Write uid/gid mappings to maintain some capabilities */ in TEST()
744 write(pipefd[1], "M", 1); /* Unable to set mappings */ in TEST()
805 return, "Cannot set uid/gid mappings"); in TEST()
867 /* Write uid/gid mappings to maintain some capabilities */ in TEST()
[all …]
/linux/include/uapi/linux/
H A Dfsmap.h19 * the lower and upper bound of mappings to return, followed by an
20 * array of struct fsmap mappings.
26 * zero, the number of reverse mappings will be returned in
27 * fmh_entries, though no mappings will be returned. fmh_reserved
/linux/arch/powerpc/platforms/cell/spufs/
H A Dspufs.h72 struct address_space *mfc; /* 'mfc' area mappings. */
73 struct address_space *cntl; /* 'control' area mappings. */
74 struct address_space *signal1; /* 'signal1' area mappings. */
75 struct address_space *signal2; /* 'signal2' area mappings. */
76 struct address_space *mss; /* 'mss' area mappings. */
77 struct address_space *psmap; /* 'psmap' area mappings. */
/linux/arch/arc/mm/
H A Dhighmem.c22 * shortlived ala "temporary mappings" which historically were implemented as
36 * This means each only has 1 PGDIR_SIZE worth of kvaddr mappings, which means
43 * mappings. However, generic pkmap code: map_new_virtual(), doesn't traverse
/linux/drivers/gpu/drm/etnaviv/
H A Detnaviv_mmu.c164 list_for_each_entry(free, &context->mappings, mmu_node) { in etnaviv_iommu_find_iova()
213 * We removed enough mappings so that the new allocation will in etnaviv_iommu_find_iova()
241 * 2. The existing buffer mappings are idle, but the buffers are not in etnaviv_iommu_insert_exact()
243 * which case the mappings will not be cleaned up and we must reap them in etnaviv_iommu_insert_exact()
287 list_add_tail(&mapping->mmu_node, &context->mappings); in etnaviv_iommu_map_gem()
312 list_add_tail(&mapping->mmu_node, &context->mappings); in etnaviv_iommu_map_gem()
440 list_add_tail(&mapping->mmu_node, &context->mappings); in etnaviv_iommu_get_suballoc_va()
/linux/Documentation/arch/x86/x86_64/
H A Dmm.rst38 … | | | | starting offset of kernel mappings.
49 … | | | | starting offset of kernel mappings.
93 from 0.125 PB to 64 PB. All kernel mappings shift down to the -64 PB starting
109 … | | | | starting offset of kernel mappings.
119 … | | | | starting offset of kernel mappings.
168 The mappings are not part of any other kernel PGD and are only available
/linux/net/netlabel/
H A Dnetlabel_cipso_v4.h6 * NetLabel system manages static and dynamic label mappings for network
128 * the CIPSO level mappings, there must be at least one
143 * the CIPSO category mappings, there must be at least one

12345678910>>...41