Searched full:unmapped (Results 1 – 25 of 49) sorted by relevance
12
| /Documentation/translations/zh_CN/mm/damon/ |
| D | design.rst | 57 <BIG UNMAPPED REGION 1>
61 <BIG UNMAPPED REGION 2>
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,sci-inta.yaml | 37 Unmapped events ---->| | umapidx |-------------------------> Globalevents
81 ti,unmapped-event-sources:
86 Array of phandles to DMA controllers where the unmapped events originate.
|
| /Documentation/arch/x86/x86_64/ |
| D | 5level-paging.rst | 49 to look for unmapped area by specified address. If it's already
50 occupied, we look for unmapped area in *full* address space, rather than
|
| /Documentation/features/vm/TLB/ |
| D | arch-support.txt | 4 # description: arch supports deferral of TLB flush until multiple pages are unmapped
|
| /Documentation/networking/device_drivers/ethernet/marvell/ |
| D | octeontx2.rst | 172 - Error due to operation of unmapped PF.
186 - Error due to unmapped slot.
236 - Receive packet on an unmapped PF.
248 - Error due to unmapped slot.
290 Rx on unmapped PF_FUNC
|
| /Documentation/userspace-api/ |
| D | tee.rst | 16 any longer it should be unmapped with munmap() to allow the reuse of
|
| D | mseal.rst | 137 apply the sealing. This is because the sealed mapping *won’t be unmapped*
|
| /Documentation/mm/damon/ |
| D | design.rst | 96 mapped to the physical memory and accessed. Thus, tracking the unmapped
100 cases. That said, too huge unmapped areas inside the monitoring target should
105 gaps between the three regions are the two biggest unmapped areas in the given
106 address space. The two biggest unmapped areas would be the gap between the
113 <BIG UNMAPPED REGION 1>
117 <BIG UNMAPPED REGION 2>
252 virtual memory could be dynamically mapped and unmapped. Physical memory could
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-reqbufs.rst | 67 orphaned and will be freed when they are unmapped or when the exported DMABUF
149 when they are unmapped or when the exported DMABUF fds are closed.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 180 of unmapped (ie free) random zones, <nr_rnd> the total number of zones,
181 <nr_unmap_seq> the number of unmapped sequential zones, and <nr_seq> the
|
| /Documentation/ABI/testing/ |
| D | sysfs-block-rnbd | 9 is using the device. When "force" is used, the device is also unmapped
|
| D | sysfs-class-rnbd-server | 32 When the device is unmapped by that client, the directory will be removed.
|
| /Documentation/mm/ |
| D | unevictable-lru.rst | 402 the old page when it is unmapped from the last VM_LOCKED VMA, and set when the
489 For each PTE (or PMD) being unmapped from a VMA, folio_remove_rmap_*() calls
514 for each PTE (or PMD) being unmapped from a VMA, folio_remove_rmap_*() calls
520 present, if one of those pages were unmapped by truncation or hole punch before
523 still appear as PG_mlocked after it has been fully unmapped: and it is left to
|
| D | multigen_lru.rst | 36 Fast paths reduce code complexity and runtime overhead. Unmapped pages
136 unmapped clean pages, which are the best bet. The eviction sorts a
|
| D | transhuge.rst | 138 page->_mapcount of anonymous pages. File pages just get unmapped.
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 396 end addresses of the unmapped area.
405 area is unmapped, either explicitly (with munmap() system call), or
410 ``UFFDIO_COPY`` on the unmapped area.
|
| D | pagemap.rst | 37 swap. Unmapped pages return a null PFN. This allows determining
43 skip over unmapped regions.
|
| D | transhuge.rst | 480 queue. This happens when a huge page is partially unmapped and
566 This happens when a huge page is partially unmapped and splitting
572 might be currently entirely mapped or have partially unmapped/unused
|
| /Documentation/networking/device_drivers/ethernet/google/ |
| D | gve.rst | 170 After the packet was successfully transmitted, the buffers are unmapped.
|
| /Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 19 through the IOMMU and faulting when encountering accesses to unmapped
|
| /Documentation/virt/kvm/devices/ |
| D | xive.rst | 57 mapped into or unmapped from the guest IRQ number space. The KVM
|
| /Documentation/gpu/ |
| D | drm-internals.rst | 134 be unmapped; on many devices, the ROM address decoder is shared with
|
| /Documentation/core-api/ |
| D | dma-api.rst | 578 For drivers that use a one-shot mapping, all ranges can be unmapped and the
602 is used to free the IOVA space. All regions must have been unmapped using
803 single] [unmapped as page]
|
| D | dma-api-howto.rst | 92 mapped only for the time they are actually used and unmapped after the DMA
302 initialization, unmapped at the end and for which the hardware should
346 transfer, unmapped right after it (unless you use dma_sync_* below)
|
| /Documentation/driver-api/driver-model/ |
| D | devres.rst | 23 iomapped address should be kept and unmapped on driver detach. For
|
12