Home
last modified time | relevance | path

Searched refs:mappings (Results 1 – 25 of 152) sorted by relevance

1234567

/Linux-v4.19/arch/arm64/
DKconfig.debug43 bool "Warn on W+X mappings at boot"
46 Generate a warning if any W+X mappings are found at boot.
49 W+X mappings after applying NX, as such mappings are a security risk.
51 mappings.
55 arm64/mm: Checked W+X mappings: passed, no W+X pages found.
59 arm64/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
62 still fine, as W+X mappings are not a security hole in
/Linux-v4.19/Documentation/arm/
Dmemory.txt53 Machine specific static mappings are also
63 PKMAP_BASE PAGE_OFFSET-1 Permanent kernel mappings
69 placed here using dynamic mappings.
71 00001000 TASK_SIZE-1 User space mappings
72 Per-thread mappings are placed here via
81 Please note that mappings which collide with the above areas may result
88 must set up their own mappings using open() and mmap().
DPorting63 address PHYS_OFFSET, along with any other mappings you supply.
79 (In other words, you can't put IO mappings below TASK_SIZE, and
95 any static mappings in this area; vmalloc will overwrite them.
/Linux-v4.19/Documentation/ia64/
Daliasing.txt60 Linux/ia64 identity mappings are done with large pages, currently
61 either 16MB or 64MB, referred to as "granules." Cacheable mappings
71 Uncacheable mappings are not speculative, so the processor will
73 software. This allows UC identity mappings to cover granules that
79 User mappings are typically done with 16K or 64K pages. The smaller
85 There are several ways the kernel creates new mappings:
89 This uses remap_pfn_range(), which creates user mappings. These
90 mappings may be either WB or UC. If the region being mapped
153 region safely with kernel page table mappings, we can use
166 succeed. It may create either WB or UC user mappings, depending
[all …]
/Linux-v4.19/Documentation/
Dnommu-mmap.txt29 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 …]
DDMA-API-HOWTO.txt35 mappings between physical and bus addresses.
181 The query for streaming mappings is performed via a call to
276 kernel will use this information later when you make DMA mappings.
315 Types of DMA mappings
318 There are two types of DMA mappings:
320 - Consistent DMA mappings which are usually mapped at driver
333 Good examples of what to use consistent mappings for are:
342 versa. Consistent mappings guarantee this.
364 - Streaming DMA mappings which are usually mapped for one DMA
371 Good examples of what to use streaming mappings for are:
[all …]
/Linux-v4.19/Documentation/vm/
Dhighmem.rst17 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
Dhugetlbfs_reserv.rst89 of mappings. Location differences are:
91 - For private mappings, the reservation map hangs off the 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 some reservations m…
[all …]
/Linux-v4.19/Documentation/arm64/
Dmemory.txt19 mappings while the user pgd contains only user (non-global) mappings.
97 mappings are created, since the host kernel runs directly in EL2.
/Linux-v4.19/arch/powerpc/platforms/powernv/
DKconfig36 bool "Enable removal of RAM from kernel mappings for tracing"
41 from the kernel mappings to be used for hardware tracing.
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-firmware-efi-runtime-map10 the same physical to virtual address mappings as the first
11 kernel. The mappings are exported to sysfs so userspace tools
/Linux-v4.19/drivers/gpu/drm/etnaviv/
Detnaviv_mmu.c163 list_for_each_entry(free, &mmu->mappings, mmu_node) { in etnaviv_iommu_find_iova()
242 list_add_tail(&mapping->mmu_node, &mmu->mappings); in etnaviv_iommu_map_gem()
263 list_add_tail(&mapping->mmu_node, &mmu->mappings); in etnaviv_iommu_map_gem()
320 INIT_LIST_HEAD(&mmu->mappings); in etnaviv_iommu_new()
Detnaviv_dump.c146 list_for_each_entry(vram, &gpu->mmu->mappings, mmu_node) { in etnaviv_core_dump()
205 list_for_each_entry(vram, &gpu->mmu->mappings, mmu_node) { in etnaviv_core_dump()
Detnaviv_mmu.h49 struct list_head mappings; member
/Linux-v4.19/Documentation/driver-api/usb/
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-v4.19/Documentation/devicetree/bindings/reserved-memory/
Dramoops.txt45 - unbuffered: if present, use unbuffered mappings to map the reserved region
46 (defaults to buffered mappings)
/Linux-v4.19/arch/x86/
DKconfig.debug102 bool "Warn on W+X mappings at boot"
105 Generate a warning if any W+X mappings are found at boot.
108 W+X mappings after applying NX, as such mappings are a security risk.
112 x86/mm: Checked W+X mappings: passed, no W+X pages found.
116 x86/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
119 still fine, as W+X mappings are not a security hole in
177 are debugging a buggy device driver that leaks IOMMU mappings.
/Linux-v4.19/Documentation/media/uapi/rc/
Drc-table-change.rst6 Changing default Remote Controller mappings
/Linux-v4.19/Documentation/netlabel/
Dcipso_ipv4.txt39 appropriate for the host. These mappings are defined as part of a CIPSO
47 mappings from the network labels to the corresponding LSM identifiers. The
/Linux-v4.19/Documentation/media/v4l-drivers/
Duvcvideo.rst21 - through mappings of XU controls to V4L2 controls
35 Control mappings
39 control mappings at runtime. These allow for individual XU controls or byte
45 The ioctl used to create these control mappings is called UVCIOC_CTRL_MAP.
115 control and a V4L2 control. Once mappings are defined, userspace
/Linux-v4.19/drivers/rapidio/devices/
Drio_mport_cdev.c180 struct list_head mappings; member
389 list_add_tail(&map->node, &md->mappings); in rio_mport_create_outbound_mapping()
405 list_for_each_entry(map, &md->mappings, node) { in rio_mport_get_outbound_mapping()
479 list_for_each_entry_safe(map, _map, &md->mappings, node) { in rio_mport_obw_free()
901 list_for_each_entry(map, &md->mappings, node) { in rio_dma_transfer()
1106 list_add_tail(&map->node, &md->mappings); in rio_mport_create_dma_mapping()
1153 list_for_each_entry_safe(map, _map, &md->mappings, node) { in rio_mport_free_dma()
1233 list_add_tail(&map->node, &md->mappings); in rio_mport_create_inbound_mapping()
1258 list_for_each_entry(map, &md->mappings, node) { in rio_mport_get_inbound_mapping()
1339 list_for_each_entry_safe(map, _map, &md->mappings, node) { in rio_mport_inbound_free()
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/ata/
Dbrcm,sata-brcm.txt12 - reg : register mappings for AHCI and SATA_TOP_CTRL
/Linux-v4.19/Documentation/devicetree/bindings/display/panel/
Dpanel-lvds.txt36 - data-mirror: If set, reverse the bit order described in the data mappings
47 LVDS data mappings are defined as follows.
/Linux-v4.19/Documentation/networking/
Dti-cpsw.txt242 INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
243 EGRESS priority mappings: 0:0 1:1 2:2 3:3 4:4 5:5 6:6 7:7
446 INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
447 EGRESS priority mappings: 0:0 1:1 2:2 3:3 4:4 5:5 6:6 7:7
500 INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
501 EGRESS priority mappings: 0:0 1:1 2:2 3:3 4:4 5:5 6:6 7:7
/Linux-v4.19/drivers/gpu/drm/omapdrm/
DTODO8 . GEM/shmem backed pages can have existing mappings (kernel linear map,

1234567