| /linux-5.19.10/Documentation/translations/zh_CN/vm/ |
| D | active_mm.rst | 59 计数器，即有多少 “真正的地址空间用户”，另一个是 “mm_count”计数器，即 “lazy”
63 一个lazy的用户仍在活动，所以你实际上得到的情况是，你有一个地址空间 **只**
64 被lazy的用户使用。这通常是一个短暂的生命周期状态，因为一旦这个线程被安排给一
68 “init_mm”应该被认为只是一个 “没有其他上下文时的lazy上下文”，事实上，它主
|
| /linux-5.19.10/kernel/ |
| D | irq_work.c | 176 struct llist_head *raised, *lazy; in irq_work_needs_cpu() local
179 lazy = this_cpu_ptr(&lazy_list); in irq_work_needs_cpu()
182 if (llist_empty(lazy)) in irq_work_needs_cpu()
|
| /linux-5.19.10/drivers/opp/ |
| D | of.c | 148 list_del(&opp_table->lazy); in _opp_table_free_required_tables()
161 bool lazy = false; in _opp_table_alloc_required_tables() local
193 lazy = true; in _opp_table_alloc_required_tables()
197 if (lazy) in _opp_table_alloc_required_tables()
198 list_add(&opp_table->lazy, &lazy_opp_tables); in _opp_table_alloc_required_tables()
363 list_for_each_entry_safe(opp_table, temp, &lazy_opp_tables, lazy) { in lazy_link_required_opp_table()
364 bool lazy = false; in lazy_link_required_opp_table() local
388 lazy = true; in lazy_link_required_opp_table()
399 lazy = false; in lazy_link_required_opp_table()
407 if (!lazy) { in lazy_link_required_opp_table()
[all …]
|
| D | opp.h | 175 struct list_head node, lazy; member
241 return unlikely(!list_empty(&opp_table->lazy)); in lazy_linking_pending()
|
| /linux-5.19.10/Documentation/vm/ |
| D | active_mm.rst | 59 and a "mm_count" counter that is the number of "lazy" users (ie anonymous
63 user exited on another CPU while a lazy user was still active, so you do
65 lazy users. That is often a short-lived state, because once that thread
70 more. "init_mm" should be considered just a "lazy context when no other
|
| /linux-5.19.10/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_irq.c | 163 bool lazy, in vmw_fallback_wait() argument
211 if (lazy) in vmw_fallback_wait()
|
| D | vmwgfx_fence.h | 94 bool lazy,
|
| D | vmwgfx_fence.c | 522 int vmw_fence_obj_wait(struct vmw_fence_obj *fence, bool lazy, in vmw_fence_obj_wait() argument
763 ret = vmw_fence_obj_wait(fence, arg->lazy, true, timeout); in vmw_fence_obj_wait_ioctl()
|
| D | vmwgfx_drv.h | 1173 bool lazy,
|
| /linux-5.19.10/Documentation/arm/ |
| D | kernel_mode_neon.rst | 30 The NEON/VFP register file is managed using lazy preserve (on UP systems) and
31 lazy restore (on both SMP and UP systems). This means that the register file is
45 mode will hit the lazy restore trap upon next use. This is handled by the
|
| /linux-5.19.10/drivers/gpu/drm/nouveau/ |
| D | nouveau_fence.h | 26 int nouveau_fence_wait(struct nouveau_fence *, bool lazy, bool intr);
|
| D | nouveau_fence.c | 324 nouveau_fence_wait(struct nouveau_fence *fence, bool lazy, bool intr) in nouveau_fence_wait() argument
328 if (!lazy) in nouveau_fence_wait()
|
| /linux-5.19.10/tools/perf/Documentation/ |
| D | perf-probe.txt | 165 3) Define event based on source file with lazy pattern
176 …ine, and '%return' means that it probes function return. And ';PTN' means lazy matching pattern (s…
177 …ber or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is the source file path, …
229 The lazy line matching is similar to glob matching but ignoring spaces in both of pattern and targe…
|
| /linux-5.19.10/include/uapi/drm/ |
| D | vmwgfx_drm.h | 646 __s32 lazy; member
|
| /linux-5.19.10/Documentation/parisc/ |
| D | registers.rst | 18 CR10 (CCR) lazy FPU saving*
|
| /linux-5.19.10/Documentation/x86/ |
| D | iommu.rst | 143 iommu: DMA domain TLB invalidation policy: lazy mode
|
| /linux-5.19.10/include/asm-generic/ |
| D | hyperv-tlfs.h | 338 u64 lazy:1; member
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | fuse.rst | 27 umounted. Note that detaching (or lazy umounting) the filesystem
199 filesystem is still attached (it hasn't been lazy unmounted)
|
| D | autofs-mount-control.rst | 23 Currently autofs uses "umount -l" (lazy umount) to clear active mounts
24 at restart. While using lazy umount works for most cases, anything that
|
| /linux-5.19.10/Documentation/driver-api/driver-model/ |
| D | devres.rst | 30 that's probably because libata low level driver developers are lazy
|
| /linux-5.19.10/Documentation/powerpc/ |
| D | transactional_memory.rst | 94 Examples are glibc's getpid() and lazy symbol resolution.
|
| /linux-5.19.10/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 140 support allocation at fault time--a.k.a lazy allocation--so hugetlbfs
142 Although hugetlbfs segments now support lazy allocation, their support
|
| /linux-5.19.10/arch/sparc/lib/ |
| D | checksum_32.S | 411 addx %g5, %g0, %g5 ! I am now to lazy to optimize this (question it
|
| /linux-5.19.10/Documentation/locking/ |
| D | ww-mutex-design.rst | 350 The Wound-Wait preemption is implemented with a lazy-preemption scheme:
|
| /linux-5.19.10/drivers/iommu/ |
| D | Kconfig | 112 DMA-mapped pages, but with "lazy" batched TLB invalidation. This
|