| /linux/drivers/iommu/iommufd/ |
| H A D | iova_bitmap.c | 16 * Main data structure for tracking mapped user pages of bitmap data.
38 /* mapped length */
93 * which u64 word of the bitmap is mapped, up to @mapped_total_index.
97 * The IOVA bitmap is usually located on what tracks DMA mapped ranges or
102 /* IOVA range representing the currently mapped bitmap data */
103 struct iova_bitmap_map mapped; member
108 /* u64 index that @mapped points to */
125 * Relative IOVA means relative to the bitmap::mapped base IOVA
126 * (stored in mapped::iova). All computations in this file are done using
127 * relative IOVAs and thus avoid an extra subtraction against mapped::iova.
[all …]
|
| /linux/tools/testing/selftests/mm/ |
| H A D | map_fixed_noreplace.c | 86 * +1 | mapped | new in main()
87 * +2 | mapped | new in main()
88 * +3 | mapped | new in main()
105 * +1 | mapped | in main()
106 * +2 | mapped | new in main()
107 * +3 | mapped | in main()
123 * +1 | mapped | in main()
124 * +2 | mapped | in main()
125 * +3 | mapped | new in main()
141 * +1 | mapped | new in main()
[all …]
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | pagemap.rst | 12 physical frame each virtual page is mapped to. It contains one 64-bit
21 * Bit 56 page exclusively mapped (since 4.2)
38 precisely which pages are mapped (or in swap) and comparing mapped
41 Traditionally, bit 56 indicates that a page is mapped exactly once and bit
42 56 is clear when a page is mapped multiple times, even when mapped in the
46 mapped in the same process, even if the page is mapped multiple times in that
48 is *maybe* mapped in a different process. In some cases, a large allocation
49 might be treated as "maybe mapped by multiple processes" even though this
53 determine which areas of memory are actually mapped and llseek to
57 times each page is mapped, indexed by PFN. Some kernel configurations do
[all …]
|
| /linux/include/linux/dma/ |
| H A D | k3-psil.h | 53 * @mapped_channel_id: PKTDMA thread to channel mapping for mapped channels.
56 * @flow_start: PKDMA flow range start of mapped channel. Unmapped
58 * @flow_num: PKDMA flow count of mapped channel. Unmapped channels
60 * @default_flow_id: PKDMA default (r)flow index of mapped channel.
61 * Must be within the flow range of the mapped channel.
75 /* PKDMA mapped channel */
77 /* PKTDMA tflow and rflow ranges for mapped channel */
|
| /linux/drivers/mtd/maps/ |
| H A D | Kconfig | 17 ROM driver code to communicate with chips which are mapped
43 are mapped on your particular target board. Refer to the
74 and RAM driver code to communicate with chips which are mapped
140 tristate "CFI Flash device mapped on AMD SC520 CDP"
148 tristate "CFI Flash device mapped on AMD NetSc520"
156 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
174 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
185 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
191 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
194 Enable support for a flash chip mapped using the DOCCS signal on a
[all …]
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| H A D | xylon,logicvc-gpio.yaml | 19 which are mapped by the driver as follows:
20 - GPIO[4:0] (display control) mapped to index 0-4
21 - EN_BLIGHT (power control) mapped to index 5
22 - EN_VDD (power control) mapped to index 6
23 - EN_VEE (power control) mapped to index 7
24 - V_EN (power control) mapped to index 8
|
| /linux/drivers/gpu/drm/msm/ |
| H A D | msm_gem_vma.c | 47 /* Don't do anything if the memory isn't mapped */ in msm_gem_vma_purge()
48 if (!vma->mapped) in msm_gem_vma_purge()
53 vma->mapped = false; in msm_gem_vma_purge()
67 if (vma->mapped) in msm_gem_vma_map()
70 vma->mapped = true; in msm_gem_vma_map()
87 vma->mapped = false; in msm_gem_vma_map()
98 GEM_WARN_ON(vma->mapped); in msm_gem_vma_close()
146 vma->mapped = false; in msm_gem_vma_init()
|
| /linux/Documentation/mm/ |
| H A D | vmalloced-kernel-stacks.rst | 4 Virtually Mapped Kernel Stack Support
15 series that introduced the `Virtually Mapped Kernel Stacks feature
25 Virtually mapped kernel stacks with guard pages cause kernel stack
30 support for virtually mapped stacks with guard pages. This feature
42 Architectures that can support Virtually Mapped Kernel Stacks should
61 mapped task stacks. This option depends on HAVE_ARCH_VMAP_STACK.
63 - Enable this if you want the use virtually-mapped kernel stacks
88 pages are mapped into contiguous kernel virtual space with PAGE_KERNEL
114 virtually mapped kernel stacks are enabled.
|
| /linux/arch/riscv/include/uapi/asm/ |
| H A D | kvm.h | 226 /* Config registers are mapped as type 1 */
231 /* Core registers are mapped as type 2 */
236 /* Control and status registers are mapped as type 3 */
248 /* Timer registers are mapped as type 4 */
253 /* F extension registers are mapped as type 5 */
258 /* D extension registers are mapped as type 6 */
263 /* ISA Extension registers are mapped as type 7 */
275 /* SBI extension registers are mapped as type 8 */
287 /* V extension registers are mapped as type 9 */
294 /* Registers for specific SBI extensions are mapped as type 10 */
[all …]
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | st,stih4xx.txt | 6 - reg: Physical base address of the IP registers and length of memory mapped region.
14 - reg: Physical base address of the IP registers and length of memory mapped region.
32 - reg: Physical base address of the IP registers and length of memory mapped region.
48 - reg: Physical base address of the IP registers and length of memory mapped region.
49 - reg-names: names of the mapped memory regions listed in regs property in
60 - reg: Physical base address of the IP registers and length of memory mapped region.
61 - reg-names: names of the mapped memory regions listed in regs property in
76 - reg: Physical base address of the IP registers and length of memory mapped region.
77 - reg-names: names of the mapped memory regions listed in regs property in
89 - reg: Physical base address of the IP registers and length of memory mapped region.
[all …]
|
| /linux/Documentation/arch/loongarch/ |
| H A D | introduction.rst | 293 LoongArch supports direct-mapped virtual memory and page-mapped virtual memory.
295 Direct-mapped virtual memory is configured by CSR.DMWn (n=0~3), it has a simple
300 Page-mapped virtual memory has arbitrary relationship between VA and PA, which
309 ``UVRANGE`` ``0x00000000 - 0x7FFFFFFF`` Page-mapped, Cached, PLV0~3
310 ``KPRANGE0`` ``0x80000000 - 0x9FFFFFFF`` Direct-mapped, Uncached, PLV0
311 ``KPRANGE1`` ``0xA0000000 - 0xBFFFFFFF`` Direct-mapped, Cached, PLV0
312 ``KVRANGE`` ``0xC0000000 - 0xFFFFFFFF`` Page-mapped, Cached, PLV0
315 User mode (PLV3) can only access UVRANGE. For direct-mapped KPRANGE0 and
317 direct-mapped VA of 0x00001000 is 0x80001000, and the cached direct-mapped
325 ``XUVRANGE`` ``0x0000000000000000 - Page-mapped, Cached, PLV0~3
[all …]
|
| /linux/tools/mm/ |
| H A D | thpmaps | 233 # dictionary of statistics describing the mapped THPs.
254 # Account pages for any partially mapped THP at the front. In that case,
259 # Account pages for any partially mapped THP at the back. In that case,
269 # Account fully mapped THPs in the middle of the range.
282 # Account PMD-mapped THPs spearately, so filter out of the stats. There is a
342 # Account blocks that are PMD-mapped spearately, so filter out of the stats.
528 pages are mapped, either system-wide, or for a specified
553 contiguously-mapped THPs whose mapping address is aligned to
555 Separate counters describe THPs mapped by PTE vs those
556 mapped by PMD. (Although note a THP can only be mapped by
[all …]
|
| /linux/include/xen/interface/ |
| H A D | features.h | 87 * A direct-mapped (or 1:1 mapped) domain is a domain for which its
88 * local pages have gfn == mfn. If a domain is direct-mapped,
93 * - not auto_translated domains (x86 only) are always direct-mapped
94 * - on x86, auto_translated domains are not direct-mapped
95 * - on ARM, Dom0 is direct-mapped, DomUs are not
|
| /linux/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| H A D | virtual-memory.json | 7 …prefetches) whose address translations missed in all TLB levels and were mapped to 1GB pages. The…
16 …prefetches) whose address translations missed in all TLB levels and were mapped to 2M or 4M pages.…
25 …prefetches) whose address translations missed in all TLB levels and were mapped to 4K pages. The …
43 …demand data stores whose address translations missed in the TLB and were mapped to 1GB pages. The…
52 …demand data stores whose address translations missed in the TLB and were mapped to 2M or 4M pages.…
61 …demand data stores whose address translations missed in the TLB and were mapped to 4K pages. The …
97 …nstruction fetches whose address translations missed in the TLB and were mapped to 1GB pages. The…
106 …nstruction fetches whose address translations missed in the TLB and were mapped to 2M or 4M pages.…
115 …nstruction fetches whose address translations missed in the TLB and were mapped to 4K pages. The …
|
| /linux/include/linux/ |
| H A D | elf-fdpic.h | 32 unsigned long elfhdr_addr; /* mapped ELF header user address */
33 unsigned long ph_addr; /* mapped PT_PHDR user address */
34 unsigned long map_addr; /* mapped loadmap user address */
35 unsigned long entry_addr; /* mapped entry user address */
37 unsigned long dynamic_addr; /* mapped PT_DYNAMIC user address */
|
| H A D | highmem-internal.h | 261 * kunmap_atomic - Unmap the virtual address mapped by kmap_atomic() - deprecated!
264 * Unmaps an address previously mapped by kmap_atomic() and re-enables
268 * Mappings should be unmapped in the reverse order that they were mapped.
271 * @__addr can be any address within the mapped page, so there is no need
283 * kunmap_local - Unmap a page mapped via kmap_local_page().
284 * @__addr: An address within the page mapped
286 * @__addr can be any address within the mapped page. Commonly it is the
|
| /linux/drivers/gpu/drm/sti/ |
| H A D | NOTES | 39 These IP are mapped to the DRM objects as following:
40 - The CRTCs are mapped to the Compositor Main and Aux Mixers
41 - The Framebuffers and planes are mapped to the Compositor GDP (non video
43 - The Cursor is mapped to the Compositor Cursor
44 - The Encoders are mapped to the TVOut
45 - The Bridges/Connectors are mapped to the HDMI / DVO / HD Analog / SD analog
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | dmx-munmap.rst | 31 Address of the mapped buffer as returned by the
35 Length of the mapped buffer. This must be the same value as given to
41 Unmaps a previously with the :c:func:`mmap()` function mapped
52 mapped yet.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | func-munmap.rst | 29 Address of the mapped buffer as returned by the
33 Length of the mapped buffer. This must be the same value as given to
43 Unmaps a previously with the :c:func:`mmap()` function mapped
54 mapped yet.
|
| /linux/include/uapi/xen/ |
| H A D | gntdev.h | 41 /* The domain ID of the grant to be mapped. */
43 /* The grant reference of the grant to be mapped. */
62 /* The number of grants to be mapped. */
96 * N.B. Where more than one page has been mapped into a contiguous range, the
105 /* The virtual address of the first mapped page in a range. */
110 /* The number of pages mapped in the VM area that begins at @vaddr. */
116 * Sets the maximum number of grants that may mapped at once by this gntdev
125 /* The maximum number of grants that may be mapped at once. */
134 * Each mapped page only supports one notification; multiple calls referring to
252 /* The domain ID of the grant references to be mapped. */
|
| /linux/drivers/remoteproc/ |
| H A D | pru_rproc.h | 18 * PRU system events are mapped to channels, and these channels are mapped
19 * to host interrupts. Events can be mapped to channels in a one-to-one or
21 * mapped to host interrupts in a one-to-one or many-to-one ratio (multiple
|
| /linux/drivers/scsi/lpfc/ |
| H A D | lpfc_mem.c | 372 * @handle: used to return the DMA-mapped address of the mbuf
374 * Description: Allocates a DMA-mapped buffer from the lpfc_mbuf_pool PCI pool.
409 * @dma: the DMA-mapped address of the lpfc_mbuf_pool to be freed
438 * @dma: the DMA-mapped address of the lpfc_mbuf_pool to be freed
463 * @handle: used to return the DMA-mapped address of the nvmet_buf
465 * Description: Allocates a DMA-mapped buffer from the lpfc_sg_dma_buf_pool
486 * @dma: the DMA-mapped address of the lpfc_sg_dma_buf_pool to be freed
500 * Description: Allocates a DMA-mapped HBQ buffer from the lpfc_hrb_pool PCI
501 * pool along a non-DMA-mapped container for it.
533 * Description: Frees both the container and the DMA-mapped buffer returned by
[all …]
|
| /linux/Documentation/input/ |
| H A D | gamepad.rst | 72 features that you need, first. How each feature is mapped is described below.
152 If analog-sticks provide digital buttons, they are mapped accordingly as
174 Menu buttons are always digital and are mapped according to their location
179 Mapped as BTN_START
183 Left button mapped as BTN_SELECT, right button mapped as BTN_START
186 and meaning. Such buttons are mapped as BTN_MODE. Examples are the Nintendo
|
| /linux/drivers/platform/chrome/ |
| H A D | cros_ec_proto.c | 259 int ret, mapped; in cros_ec_get_host_event_wake_mask() local
272 mapped = cros_ec_map_error(msg->result); in cros_ec_get_host_event_wake_mask()
273 if (mapped) { in cros_ec_get_host_event_wake_mask()
274 ret = mapped; in cros_ec_get_host_event_wake_mask()
353 int ret, mapped; in cros_ec_get_proto_info() local
375 mapped = cros_ec_map_error(msg->result); in cros_ec_get_proto_info()
376 if (mapped) { in cros_ec_get_proto_info()
377 ret = mapped; in cros_ec_get_proto_info()
423 int ret, mapped; in cros_ec_get_proto_info_legacy() local
444 mapped = cros_ec_map_error(msg->result); in cros_ec_get_proto_info_legacy()
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/grandridge/ |
| H A D | virtual-memory.json | 23 …lations missed in all Translation Lookaside Buffer (TLB) levels and were mapped to 2M or 4M pages.…
32 …lations missed in all Translation Lookaside Buffer (TLB) levels and were mapped to 4K pages. Inclu…
66 …lations missed in all Translation Lookaside Buffer (TLB) levels and were mapped to 2M or 4M pages.…
75 …lations missed in all Translation Lookaside Buffer (TLB) levels and were mapped to 4K pages. Incl…
109 …lations missed in all Translation Lookaside Buffer (TLB) levels and were mapped to any page size. …
118 …lations missed in all Translation Lookaside Buffer (TLB) levels and were mapped to 2M or 4M pages.…
127 …lations missed in all Translation Lookaside Buffer (TLB) levels and were mapped to 4K pages. Incl…
|