| /Linux-v5.4/arch/arm64/ |
| D | Kconfig.debug | 44 bool "Warn on W+X mappings at boot"
47 Generate a warning if any W+X mappings are found at boot.
50 W+X mappings after applying NX, as such mappings are a security risk.
52 mappings.
56 arm64/mm: Checked W+X mappings: passed, no W+X pages found.
60 arm64/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
63 still fine, as W+X mappings are not a security hole in
|
| /Linux-v5.4/Documentation/ia64/ |
| D | aliasing.rst | 64 Kernel Identify Mappings
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
84 User Mappings
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
[all …]
|
| /Linux-v5.4/arch/x86/include/asm/ |
| D | invpcid.h | 13 * mappings, we don't want the compiler to reorder any subsequent in __invpcid()
28 /* Flush all mappings for a given pcid and addr, not including globals. */
35 /* Flush all mappings for a given PCID, not including globals. */
41 /* Flush all mappings, including globals, for all PCIDs. */
47 /* Flush all mappings for all PCIDs except globals. */
|
| D | fixmap.h | 96 FIX_KMAP_BEGIN, /* reserved pte's for temporary kernel mappings */
118 * 512 temporary boot-time mappings, used by early_ioremap(),
178 * Early memremap routines used for in-place encryption. The mappings created
179 * by these routines are intended to be used as temporary mappings.
|
| /Linux-v5.4/Documentation/ |
| D | nommu-mmap.txt | 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 | DMA-API-HOWTO.txt | 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.4/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.4/Documentation/vm/ |
| D | highmem.rst | 17 at all times. This means the kernel needs to start using temporary mappings of
50 Temporary Virtual Mappings
53 The kernel contains several ways of creating temporary mappings:
67 CPU until it has finished, lest some other task displace its mappings.
110 Cost of Temporary 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.4/arch/x86/mm/ |
| D | mem_encrypt_identity.c | 13 * Since we're dealing with identity mappings, physical and virtual
249 * entries that are needed. Those mappings will be covered mostly in sme_pgtable_calc()
252 * mappings. For mappings that are not 2MB aligned, PTE mappings in sme_pgtable_calc()
349 * One PGD for both encrypted and decrypted mappings and a set of in sme_encrypt_kernel()
350 * PUDs and PMDs for each of the encrypted and decrypted mappings. in sme_encrypt_kernel()
375 * mappings are populated. in sme_encrypt_kernel()
396 * decrypted kernel mappings are created. in sme_encrypt_kernel()
417 /* Add encrypted kernel (identity) mappings */ in sme_encrypt_kernel()
423 /* Add decrypted, write-protected kernel (non-identity) mappings */ in sme_encrypt_kernel()
430 /* Add encrypted initrd (identity) mappings */ in sme_encrypt_kernel()
[all …]
|
| /Linux-v5.4/arch/sh/mm/ |
| D | pmb.c | 50 /* 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-v5.4/arch/arm64/mm/ |
| D | pageattr.c | 69 * Kernel VA mappings are always live, and splitting live section in change_memory_common()
70 * mappings into page mappings may cause TLB conflicts. This means in change_memory_common()
74 * Let's restrict ourselves to mappings created by vmalloc (or vmap). in change_memory_common()
75 * Those are guaranteed to consist entirely of page mappings, and in change_memory_common()
195 * p?d_present(). When debug_pagealloc is enabled, sections mappings are
|
| /Linux-v5.4/drivers/misc/mic/host/ |
| D | mic_smpt.h | 24 * @ref_count: Number of active mappings for this SMPT entry in bytes.
50 * @ref_count: Number of active SMPT mappings (for debug).
51 * @map_count: Number of SMPT mappings created (for debug).
52 * @unmap_count: Number of SMPT mappings destroyed (for debug).
|
| /Linux-v5.4/arch/hexagon/include/asm/ |
| D | mem-layout.h | 71 * 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-v5.4/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.4/arch/x86/ |
| D | Kconfig.debug | 92 bool "Warn on W+X mappings at boot"
95 Generate a warning if any W+X mappings are found at boot.
98 W+X mappings after applying NX, as such mappings are a security risk.
102 x86/mm: Checked W+X mappings: passed, no W+X pages found.
106 x86/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
109 still fine, as W+X mappings are not a security hole in
167 are debugging a buggy device driver that leaks IOMMU mappings.
|
| /Linux-v5.4/include/drm/ |
| D | drm_cache.h | 54 * for some buffers, both the CPU and the GPU use uncached mappings, in drm_arch_can_wc_memory()
57 * The use of uncached GPU mappings relies on the correct implementation in drm_arch_can_wc_memory()
59 * will use cached mappings nonetheless. On x86 platforms, this does not in drm_arch_can_wc_memory()
60 * seem to matter, as uncached CPU mappings will snoop the caches in any in drm_arch_can_wc_memory()
|
| /Linux-v5.4/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.4/arch/sh/kernel/ |
| D | head_32.S | 91 * Reconfigure the initial PMB mappings setup by the hardware.
102 * our address space and the initial mappings may not map PAGE_OFFSET
105 * Once we've setup cached and uncached mappings we clear the rest of the
156 * existing mappings that match the initial mappings VPN/PPN.
175 cmp/eq r0, r8 /* Check for valid __MEMORY_START mappings */
185 * mappings.
|
| /Linux-v5.4/arch/arc/mm/ |
| D | highmem.c | 22 * shortlived ala "temporary mappings" which historically were implemented as
36 * This means each only has 1 PGDIR_SIZE worth of kvaddr mappings, which means
39 * - fixmap anyhow needs a limited number of mappings. So 2M kvaddr == 256 PTE
44 * mappings. However, generic pkmap code: map_new_virtual(), doesn't traverse
|
| /Linux-v5.4/include/uapi/linux/ |
| D | fsmap.h | 19 * 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-v5.4/drivers/iommu/ |
| D | virtio-iommu.c | 71 struct rb_root_cached mappings; member
330 interval_tree_insert(&mapping->iova, &vdomain->mappings); in viommu_add_mapping()
337 * viommu_del_mappings - remove mappings from the internal tree
356 next = interval_tree_iter_first(&vdomain->mappings, iova, last); in viommu_del_mappings()
372 interval_tree_remove(node, &vdomain->mappings); in viommu_del_mappings()
384 * mappings were deleted from the device. Re-create the mappings available in
396 node = interval_tree_iter_first(&vdomain->mappings, 0, -1UL); in viommu_replay_mappings()
600 vdomain->mappings = RB_ROOT_CACHED; in viommu_domain_alloc()
637 /* Free all remaining mappings (size 2^64) */ in viommu_domain_free()
674 * old domain isn't attached to any endpoint, all mappings are removed in viommu_attach_dev()
[all …]
|
| D | msm_iommu.h | 12 /* 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-v5.4/arch/powerpc/platforms/cell/spufs/ |
| D | spufs.h | 72 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-v5.4/include/linux/iio/ |
| D | driver.h | 17 * @map: array of mappings specifying association of channel with client
23 * iio_map_array_unregister() - tell the core to remove consumer mappings for
|
