| /Linux-v5.10/drivers/gpu/drm/panfrost/ |
| D | panfrost_gem.c | 36 WARN_ON_ONCE(!list_empty(&bo->mappings.list)); in panfrost_gem_free_object()
61 mutex_lock(&bo->mappings.lock); in panfrost_gem_mapping_get()
62 list_for_each_entry(iter, &bo->mappings.list, node) { in panfrost_gem_mapping_get()
69 mutex_unlock(&bo->mappings.lock); in panfrost_gem_mapping_get()
112 list_for_each_entry(mapping, &bo->mappings.list, node) in panfrost_gem_teardown_mappings_locked()
160 mutex_lock(&bo->mappings.lock); in panfrost_gem_open()
162 list_add_tail(&mapping->node, &bo->mappings.list); in panfrost_gem_open()
163 mutex_unlock(&bo->mappings.lock); in panfrost_gem_open()
177 mutex_lock(&bo->mappings.lock); in panfrost_gem_close()
178 list_for_each_entry(iter, &bo->mappings.list, node) { in panfrost_gem_close()
[all …]
|
| D | panfrost_drv.c | 152 job->mappings = kvmalloc_array(job->bo_count, in panfrost_lookup_bos()
155 if (!job->mappings) in panfrost_lookup_bos()
169 job->mappings[i] = mapping; in panfrost_lookup_bos()
403 mutex_lock(&bo->mappings.lock); in panfrost_ioctl_madvise()
407 first = list_first_entry(&bo->mappings.list, in panfrost_ioctl_madvise()
419 if (!list_is_singular(&bo->mappings.list) || in panfrost_ioctl_madvise()
437 mutex_unlock(&bo->mappings.lock); in panfrost_ioctl_madvise()
|
| D | panfrost_gem_shrinker.c | 48 if (!mutex_trylock(&bo->mappings.lock)) in panfrost_gem_purge()
61 mutex_unlock(&bo->mappings.lock); in panfrost_gem_purge()
|
| D | panfrost_job.c | 271 if (job->mappings) { in panfrost_job_cleanup()
273 if (!job->mappings[i]) in panfrost_job_cleanup()
276 atomic_dec(&job->mappings[i]->obj->gpu_usecount); in panfrost_job_cleanup()
277 panfrost_gem_mapping_put(job->mappings[i]); in panfrost_job_cleanup()
279 kvfree(job->mappings); in panfrost_job_cleanup()
|
| D | panfrost_job.h | 35 struct panfrost_gem_mapping **mappings; member
|
| /Linux-v5.10/Documentation/arm/ |
| D | memory.rst | 57 Machine specific static mappings are also
67 PKMAP_BASE PAGE_OFFSET-1 Permanent kernel mappings
73 placed here using dynamic mappings.
75 00001000 TASK_SIZE-1 User space mappings
76 Per-thread mappings are placed here via
86 Please note that mappings which collide with the above areas may result
93 must set up their own mappings using open() and mmap().
|
| /Linux-v5.10/Documentation/ia64/ |
| D | aliasing.rst | 67 Linux/ia64 identity mappings are done with large pages, currently
68 either 16MB or 64MB, referred to as "granules." Cacheable mappings
78 Uncacheable mappings are not speculative, so the processor will
80 software. This allows UC identity mappings to cover granules that
87 User mappings are typically done with 16K or 64K pages. The smaller
94 There are several ways the kernel creates new mappings:
99 This uses remap_pfn_range(), which creates user mappings. These
100 mappings may be either WB or UC. If the region being mapped
167 region safely with kernel page table mappings, we can use
182 succeed. It may create either WB or UC user mappings, depending
[all …]
|
| /Linux-v5.10/drivers/soc/aspeed/ |
| D | Kconfig | 12 Control Aspeed ast2400/2500 HOST LPC to BMC mappings through
28 Control Aspeed ast2400/2500 HOST P2A VGA MMIO to BMC mappings through
29 ioctl()s, the driver also provides an interface for userspace mappings to
|
| /Linux-v5.10/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 …]
|
| /Linux-v5.10/mm/ |
| D | Kconfig.debug | 125 bool "Warn on W+X mappings at boot"
130 Generate a warning if any W+X mappings are found at boot.
133 mappings after applying NX, as such mappings are a security risk.
137 <arch>/mm: Checked W+X mappings: passed, no W+X pages found.
141 <arch>/mm: Checked W+X mappings: failed, <N> W+X pages found.
144 still fine, as W+X mappings are not a security hole in
|
| /Linux-v5.10/Documentation/devicetree/bindings/ |
| D | .yamllint | 31 forbid-in-block-mappings: true
32 forbid-in-flow-mappings: true
|
| /Linux-v5.10/Documentation/vm/ |
| D | highmem.rst | 17 at all times. This means the kernel needs to start using temporary mappings of
53 The kernel contains several ways of creating temporary mappings:
67 CPU until it has finished, lest some other task displace its mappings.
113 The cost of creating temporary mappings can be quite high. The arch has to
118 a pointer to the page contents rather than juggling mappings about. In such a
121 If CONFIG_MMU is not set, then there can be no temporary mappings and no
|
| D | hugetlbfs_reserv.rst | 89 of mappings. Location differences are:
91 - For private mappings, the reservation map hangs off the VMA structure.
94 - For shared mappings, the reservation map hangs off the inode. Specifically,
95 inode->i_mapping->private_data. Since shared mappings are always backed
123 One of the big differences between PRIVATE and SHARED mappings is the way
126 - For shared mappings, an entry in the reservation map indicates a reservation
129 - For private mappings, the lack of an entry in the reservation map indicates
135 For private mappings, hugetlb_reserve_pages() creates the reservation map and
140 are needed for the current mapping/segment. For private mappings, this is
141 always the value (to - from). However, for shared mappings it is possible that
[all …]
|
| /Linux-v5.10/arch/powerpc/platforms/powernv/ |
| D | Kconfig | 30 bool "Enable removal of RAM from kernel mappings for tracing"
34 from the kernel mappings to be used for hardware tracing.
|
| /Linux-v5.10/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
|
| /Linux-v5.10/Documentation/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 | 24 mappings while the user pgd contains only user (non-global) mappings.
40 fffffdfffe5f9000 fffffdfffe9fffff 4124KB fixed mappings
60 fffffc1ffe590000 fffffc1ffe9fffff 4544KB fixed mappings
106 mappings are created, since the host kernel runs directly in EL2.
|
| /Linux-v5.10/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.)
|
| /Linux-v5.10/drivers/gpu/drm/etnaviv/ |
| D | etnaviv_mmu.c | 157 list_for_each_entry(free, &context->mappings, mmu_node) { in etnaviv_iommu_find_iova()
243 list_add_tail(&mapping->mmu_node, &context->mappings); in etnaviv_iommu_map_gem()
269 list_add_tail(&mapping->mmu_node, &context->mappings); in etnaviv_iommu_map_gem()
392 list_add_tail(&mapping->mmu_node, &context->mappings); in etnaviv_iommu_get_suballoc_va()
|
| /Linux-v5.10/Documentation/userspace-api/media/rc/ |
| D | rc-table-change.rst | 6 Changing default Remote Controller mappings
|
| /Linux-v5.10/Documentation/x86/x86_64/ |
| D | mm.rst | 37 … | | | | starting offset of kernel mappings.
81 from 0.125 PB to 64 PB. All kernel mappings shift down to the -64 PB starting
96 … | | | | starting offset of kernel mappings.
149 The mappings are not part of any other kernel PGD and are only available
|
| /Linux-v5.10/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
214 coherent allocations, but supports full 64-bits for streaming mappings
237 kernel will use this information later when you make DMA mappings.
276 Types of DMA mappings
279 There are two types of DMA mappings:
281 - Consistent DMA mappings which are usually mapped at driver
294 Good examples of what to use consistent mappings for are:
303 versa. Consistent mappings guarantee this.
325 - Streaming DMA mappings which are usually mapped for one DMA
[all …]
|
| /Linux-v5.10/drivers/iommu/ |
| D | virtio-iommu.c | 71 struct rb_root_cached mappings; member
329 interval_tree_insert(&mapping->iova, &vdomain->mappings); in viommu_add_mapping()
355 next = interval_tree_iter_first(&vdomain->mappings, iova, last); in viommu_del_mappings()
371 interval_tree_remove(node, &vdomain->mappings); in viommu_del_mappings()
395 node = interval_tree_iter_first(&vdomain->mappings, 0, -1UL); in viommu_replay_mappings()
599 vdomain->mappings = RB_ROOT_CACHED; in viommu_domain_alloc()
801 node = interval_tree_iter_first(&vdomain->mappings, iova, iova); in viommu_iova_to_phys()
|
| /Linux-v5.10/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
|
| /Linux-v5.10/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
|
