Searched full:mapping (Results 1 – 25 of 579) sorted by relevance
12345678910>>...24
| /Documentation/driver-api/ |
| D | io-mapping.rst | 8 The io_mapping functions in linux/io-mapping.h provide an abstraction for
9 efficiently mapping small regions of an I/O device to the CPU. The initial
14 A mapping object is created during driver initialization using::
20 mappable, while 'size' indicates how large a mapping region to
23 This _wc variant provides a mapping which may only be used with
27 With this mapping object, individual pages can be mapped either temporarily
31 void *io_mapping_map_local_wc(struct io_mapping *mapping,
34 void *io_mapping_map_atomic_wc(struct io_mapping *mapping,
37 'offset' is the offset within the defined mapping region. Accessing
46 Temporary mappings are only valid in the context of the caller. The mapping
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
7 mapping is made use of in conjunction with the mmap() system call, the shmat()
9 mapping is actually performed by the binfmt drivers, which call back into the
12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
19 (#) Anonymous mapping, MAP_PRIVATE
27 (#) Anonymous mapping, MAP_SHARED
37 the underlying file are reflected in the mapping; copied across fork.
41 - If one exists, the kernel will re-use an existing mapping to the
45 - If possible, the file mapping will be directly on the backing device
[all …]
|
| /Documentation/filesystems/iomap/ |
| D | design.rst | 70 of mapping function calls into the filesystem across a larger amount of
78 1. Obtain a space mapping via ``->iomap_begin``
82 1. Revalidate the mapping and go back to (1) above, if necessary.
89 4. Release the mapping via ``->iomap_end``, if necessary
130 * **filesystem mapping lock**: This synchronization primitive is
131 internal to the filesystem and must protect the file mapping data
132 from updates while a mapping is being sampled.
138 mapping.
154 The filesystem communicates to the iomap iterator the mapping of
177 bytes, covered by this mapping.
[all …]
|
| D | porting.rst | 24 into the filesystem to return a mapping for only that page.
55 mapping of a file range.
62 other read-only mapping operations will do the right thing.
67 Hide behind a debugging knob the ability to switch on the iomap mapping
70 mapping information from the ``iomap`` structure, but the new functions
93 It is strongly recommended to create separate mapping functions and
98 write mapping implementation introduces.
101 This will get the entire filesystem using the new mapping functions, and
106 The mapping functions should all work correctly, so all that needs to be
|
| /Documentation/core-api/ |
| D | dma-attributes.rst | 6 defined in linux/dma-mapping.h.
11 DMA_ATTR_WEAK_ORDERING specifies that reads and writes to the mapping
21 DMA_ATTR_WRITE_COMBINE specifies that writes to the mapping may be
32 virtual mapping for the allocated buffer. On some architectures creating
33 such mapping is non-trivial task and consumes very limited resources
52 having a mapping created separately for each device and is usually
67 device domain after releasing a mapping for it. Use this attribute with
73 By default DMA-mapping subsystem is allowed to assemble the buffer
82 This is a hint to the DMA-mapping subsystem that it's probably not worth
84 efficiency (AKA it's not worth trying to build the mapping out of larger
[all …]
|
| /Documentation/arch/riscv/ |
| D | boot.rst | 14 mapping is set up.
40 PMPs, in the direct mapping, so the firmware must correctly mark those regions
117 Virtual mapping installation
120 The installation of the virtual mapping is done in 2 steps in the RISC-V kernel:
122 1. ``setup_vm()`` installs a temporary kernel mapping in ``early_pg_dir`` which
124 at this point. When establishing this mapping, no allocation can be done
128 2. ``setup_vm_final()`` creates the final kernel mapping in ``swapper_pg_dir``
130 mapping. When establishing this mapping, the kernel can allocate memory but
131 cannot access it directly (since the direct mapping is not present yet), so
136 direct mapping addresses to physical addresses, they need to know the start of
[all …]
|
| /Documentation/mm/ |
| D | highmem.rst | 18 The part of (physical) memory not covered by a permanent mapping is what we
64 These mappings are thread-local and CPU-local, meaning that the mapping
66 CPU while the mapping is active. Although preemption is never disabled by
68 CPU-hotplug until the mapping is disposed.
71 in which the local mapping is acquired does not allow it for other reasons.
82 virtual address of the direct mapping. Only real highmem pages are
95 therefore try to design their code to avoid the use of kmap() by mapping
107 NOTE: Conversions to kmap_local_page() must take care to follow the mapping
116 This permits a very short duration mapping of a single page. Since the
117 mapping is restricted to the CPU that issued it, it performs well, but
[all …]
|
| D | hugetlbfs_reserv.rst | 15 huge pages to cover the mapping, the mmap() would fail. This was first
17 were enough free huge pages to cover the mapping. Like most things in the
20 available for page faults in that mapping. The description below attempts to
50 There is one reserve map for each huge page mapping in the system.
52 the mapping. A region is described as::
61 indices into the mapping. Depending on the type of mapping, a
69 associated with the mapping.
71 Indicates task originally mapping this range (and creating
83 A huge page mapping or segment is either private or shared. If private,
91 time the mapping (mmap(MAP_PRIVATE)) is created.
[all …]
|
| D | remap_file_pages.rst | 5 The remap_file_pages() system call is used to create a nonlinear mapping,
6 that is, a mapping in which the pages of the file are mapped into a
12 Supporting of nonlinear mapping requires significant amount of non-trivial
14 nonlinear mapping work kernel need a way to distinguish normal page table
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,wcd939x-sdw.yaml | 23 qcom,tx-port-mapping:
25 Specifies static port mapping between device and host tx ports.
31 qcom,rx-port-mapping:
33 Specifies static port mapping between device and host rx ports.
54 qcom,rx-port-mapping = <1 2 3 4 5 6>;
65 qcom,tx-port-mapping = <2 3 4 5>;
|
| D | qcom,wcd938x-sdw.yaml | 24 qcom,tx-port-mapping:
26 Specifies static port mapping between slave and master tx ports.
32 qcom,rx-port-mapping:
34 Specifies static port mapping between slave and master rx ports.
55 qcom,rx-port-mapping = <1 2 3 4 5>;
66 qcom,tx-port-mapping = <2 3 4 5>;
|
| D | st,sta32x.txt | 34 - st,ch1-output-mapping: Channel 1 output mapping
35 - st,ch2-output-mapping: Channel 2 output mapping
36 - st,ch3-output-mapping: Channel 3 output mapping
93 st,ch1-output-mapping = /bits/ 8 <0>; // set channel 1 output ch 1
94 st,ch2-output-mapping = /bits/ 8 <0>; // set channel 2 output ch 1
95 st,ch3-output-mapping = /bits/ 8 <0>; // set channel 3 output ch 1
|
| D | st,sta350.txt | 30 - st,ch1-output-mapping: Channel 1 output mapping
31 - st,ch2-output-mapping: Channel 2 output mapping
32 - st,ch3-output-mapping: Channel 3 output mapping
123 st,ch1-output-mapping = /bits/ 8 <0>; // set channel 1 output ch 1
124 st,ch2-output-mapping = /bits/ 8 <0>; // set channel 2 output ch 1
125 st,ch3-output-mapping = /bits/ 8 <0>; // set channel 3 output ch 1
|
| D | qcom,wcd937x-sdw.yaml | 24 qcom,tx-port-mapping:
26 Specifies static port mapping between device and host tx ports.
42 qcom,rx-port-mapping:
44 Specifies static port mapping between device and host rx ports.
76 qcom,rx-port-mapping = <1 2 3 4 5>;
87 qcom,tx-port-mapping = <2 2 3 4>;
|
| /Documentation/arch/xtensa/ |
| D | booting.rst | 14 the address must be a valid address in the current mapping. The kernel will
15 not change the mapping on its own.
17 default virtual mapping (0xd0000000..0xffffffff).
20 virtual mapping. It is considered physical if it is within the range of
21 physical addresses covered by the default KSEG mapping (XCHAL_KSEG_PADDR..
|
| /Documentation/arch/arm/ |
| D | memory.rst | 26 setup a minicache mapping.
42 fffe8000 fffeffff DTCM mapping area for platforms with
45 fffe0000 fffe7fff ITCM mapping area for platforms with
48 ffc80000 ffefffff Fixmap mapping region. Addresses provided
53 ff800000 ffbfffff Permanent, fixed read-only mapping of the
56 fee00000 feffffff Mapping of PCI I/O space. This is a static
57 mapping within the vmalloc space.
73 One way of mapping HIGHMEM pages into kernel
93 space are also caught via this mapping.
100 Since future CPUs may impact the kernel mapping layout, user programs
|
| /Documentation/core-api/irq/ |
| D | irq-domain.rst | 2 The irq_domain interrupt number mapping library
28 irq numbers, but they don't provide any support for reverse mapping of
32 The irq_domain library adds mapping between hwirq and IRQ numbers on
33 top of the irq_alloc_desc*() API. An irq_domain to manage mapping is
35 reverse mapping scheme.
46 (each mapping method has a different allocator function, more on that later).
53 hwirq number as arguments. If a mapping for the hwirq doesn't already
58 Once a mapping has been established, it can be retrieved or used via a
63 mapping.
65 hwirq number, and 0 if there was no mapping
[all …]
|
| /Documentation/trace/ |
| D | ring-buffer-map.rst | 4 Tracefs ring-buffer memory mapping
12 as no memory copy is necessary. The application mapping the ring-buffer becomes
15 Memory mapping setup
17 The mapping works with a mmap() of the trace_pipe_raw interface.
19 The first system page of the mapping contains ring-buffer statistics and
25 therefore effortless to know where the reader starts in the mapping:
38 When a mapping is in place on a Tracefs ring-buffer, it is not possible to
43 Concurrent readers (either another application mapping that ring-buffer or the
|
| /Documentation/devicetree/bindings/display/ |
| D | lvds-data-mapping.yaml | 4 $id: http://devicetree.org/schemas/display/lvds-data-mapping.yaml#
7 title: LVDS Data Mapping
30 data-mapping:
36 The color signals mapping order.
40 - "jeida-18" - 18-bit data mapping compatible with the [JEIDA], [LDI] and
51 - "jeida-24" - 24-bit data mapping compatible with the [DSIM] and [LDI]
63 - "vesa-24" - 24-bit data mapping compatible with the [VESA] specification.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 70 mapping of the logical device blocks. The mapping is done per chunk of
72 mapping table is indexed by chunk number and each mapping entry
74 mapping entry may also indicate if the zone number of a conventional
78 blocks in the data zones follows the mapping table. A valid block is
80 data chunk, a block is always valid only in the data zone mapping the
84 are processed by directly writing to the zone. If the mapping zone is a
92 automatically invalidate the same block in the sequential zone mapping
94 is freed and the chunk buffer zone becomes the primary zone mapping the
100 the sequential zone mapping a chunk, or if the chunk is buffered, from
101 the buffer zone assigned. If the accessed chunk has no mapping, or the
[all …]
|
| /Documentation/arch/powerpc/ |
| D | vmemmap_dedup.rst | 14 With 2M PMD level mapping, we require 32 struct pages and a single 64K vmemmap
18 With 1G PUD level mapping, we require 16384 struct pages and a single 64K
20 require 16 64K pages in vmemmap to map the struct page for 1G PUD level mapping.
23 +-----------+ ---virt_to_page---> +-----------+ mapping to +-----------+
35 | mapping | +-----------+ | |
46 With 4K page size, 2M PMD level mapping requires 512 struct pages and a single
48 require 8 4K pages in vmemmap to map the struct page for 2M pmd level mapping.
52 +-----------+ ---virt_to_page---> +-----------+ mapping to +-----------+
64 | mapping | +-----------+ | |
74 With 1G PUD level mapping, we require 262144 struct pages and a single 4K
[all …]
|
| /Documentation/userspace-api/ |
| D | mseal.rst | 14 Memory sealing additionally protects the mapping itself against
72 Once mapping is sealed, it can't be unsealed. The kernel should never
76 Blocked mm syscall for sealed mapping
78 It might be important to note: **once the mapping is sealed, it will
99 replacement with a new mapping with new set of attributes, or can
100 overwrite the existing mapping with another mapping.
103 protection bits (RWX) of the mapping.
129 mapping segments.
136 but it is *crucial to thoroughly analyze the mapping's lifetime* prior to
137 apply the sealing. This is because the sealed mapping *won’t be unmapped*
[all …]
|
| /Documentation/translations/zh_CN/mm/ |
| D | page_migration.rst | 143 2. ``int (*migratepage) (struct address_space *mapping,``
168 void __SetPageMovable(struct page *page, struct address_space *mapping)
175 page->mapping = page->mapping | PAGE_MAPPING_MOVABLE;
177 所以驱动不应该直接访问page->mapping。相反，驱动应该使用page_mapping()，它可
190 mapping->a_ops->isolate_page。lock_page()可以防止突然破坏page->mapping。
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | cpus.txt | 24 - fsl,portid-mapping
27 Definition: The Coherency Subdomain ID Port Mapping Registers and
28 Snoop ID Port Mapping registers, which are part of the CoreNet
30 ID/CoreNet Snoop ID to cpu mapping functions. Certain bits from
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | ppc440spe-adma.txt | 16 - reg : <registers mapping>
35 - reg : <registers mapping>
37 - interrupts : <interrupt mapping for DMA0/1 interrupts sources:
65 - reg : <registers mapping>
66 - interrupts : <interrupt mapping for XOR interrupt source>
|
12345678910>>...24