| /Linux-v6.6/Documentation/translations/zh_CN/mm/ |
| D | active_mm.rst | 59 计数器，即有多少 “真正的地址空间用户”，另一个是 “mm_count”计数器，即 “lazy”
63 一个lazy的用户仍在活动，所以你实际上得到的情况是，你有一个地址空间 **只**
64 被lazy的用户使用。这通常是一个短暂的生命周期状态，因为一旦这个线程被安排给一
68 “init_mm”应该被认为只是一个 “没有其他上下文时的lazy上下文”，事实上，它主
|
| /Linux-v6.6/Documentation/mm/ |
| D | active_mm.rst | 5 Note, the mm_count refcount may no longer include the "lazy" users
7 with CONFIG_MMU_LAZY_TLB_REFCOUNT=n. Taking and releasing these lazy
63 and a "mm_count" counter that is the number of "lazy" users (ie anonymous
67 user exited on another CPU while a lazy user was still active, so you do
69 lazy users. That is often a short-lived state, because once that thread
74 more. "init_mm" should be considered just a "lazy context when no other
|
| /Linux-v6.6/kernel/ |
| D | irq_work.c | 186 struct llist_head *raised, *lazy; in irq_work_needs_cpu() local
189 lazy = this_cpu_ptr(&lazy_list); in irq_work_needs_cpu()
192 if (llist_empty(lazy)) in irq_work_needs_cpu()
|
| /Linux-v6.6/kernel/rcu/ |
| D | tree_nocb.h | 331 unsigned long j, bool lazy) in rcu_nocb_do_flush_bypass() argument
353 if (lazy && rhp) { in rcu_nocb_do_flush_bypass()
375 unsigned long j, bool lazy) in rcu_nocb_flush_bypass() argument
381 return rcu_nocb_do_flush_bypass(rdp, rhp, j, lazy); in rcu_nocb_flush_bypass()
417 bool lazy) in rcu_nocb_try_bypass() argument
469 if (rdp->nocb_nobypass_count < nocb_nobypass_lim_per_jiffy && !lazy) { in rcu_nocb_try_bypass()
490 if (!rcu_nocb_flush_bypass(rdp, rhp, j, lazy)) { in rcu_nocb_try_bypass()
519 if (lazy) in rcu_nocb_try_bypass()
535 if (ncbs && (!bypass_is_lazy || lazy)) { in rcu_nocb_try_bypass()
685 bool lazy = false; in nocb_gp_wait() local
[all …]
|
| D | tree.h | 465 unsigned long j, bool lazy);
468 bool lazy);
|
| /Linux-v6.6/drivers/opp/ |
| D | of.c | 153 list_del(&opp_table->lazy); in _opp_table_free_required_tables()
167 bool lazy = false; in _opp_table_alloc_required_tables() local
199 lazy = true; in _opp_table_alloc_required_tables()
203 if (lazy) { in _opp_table_alloc_required_tables()
209 list_add(&opp_table->lazy, &lazy_opp_tables); in _opp_table_alloc_required_tables()
384 list_for_each_entry_safe(opp_table, temp, &lazy_opp_tables, lazy) { in lazy_link_required_opp_table()
385 bool lazy = false; in lazy_link_required_opp_table() local
409 lazy = true; in lazy_link_required_opp_table()
420 lazy = false; in lazy_link_required_opp_table()
428 if (!lazy) { in lazy_link_required_opp_table()
[all …]
|
| D | opp.h | 195 struct list_head node, lazy; member
263 return unlikely(!list_empty(&opp_table->lazy)); in lazy_linking_pending()
|
| /Linux-v6.6/drivers/crypto/intel/qat/qat_common/ |
| D | icp_qat_hw_20_comp.h | 69 __u16 lazy; member
102 QAT_FIELD_SET(val32, csr.lazy, in ICP_QAT_FW_COMP_20_BUILD_CONFIG_UPPER()
|
| D | adf_gen4_dc.c | 42 hw_comp_upper_csr.lazy = ICP_QAT_HW_COMP_20_CONFIG_CSR_LAZY_PARAM_DEFAULT_VAL; in qat_comp_build_deflate()
|
| /Linux-v6.6/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()
|
| /Linux-v6.6/Documentation/arch/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-v6.6/drivers/gpu/drm/nouveau/ |
| D | nouveau_fence.h | 26 int nouveau_fence_wait(struct nouveau_fence *, bool lazy, bool intr);
|
| D | nouveau_fence.c | 328 nouveau_fence_wait(struct nouveau_fence *fence, bool lazy, bool intr) in nouveau_fence_wait() argument
332 if (!lazy) in nouveau_fence_wait()
|
| /Linux-v6.6/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-v6.6/include/uapi/drm/ |
| D | vmwgfx_drm.h | 646 __s32 lazy; member
|
| /Linux-v6.6/Documentation/arch/parisc/ |
| D | registers.rst | 18 CR10 (CCR) lazy FPU saving*
|
| /Linux-v6.6/Documentation/arch/x86/ |
| D | iommu.rst | 143 iommu: DMA domain TLB invalidation policy: lazy mode
|
| /Linux-v6.6/include/asm-generic/ |
| D | hyperv-tlfs.h | 355 u64 lazy:1; member
|
| /Linux-v6.6/arch/ |
| D | Kconfig | 484 # "lazy tlb" beyond its final refcount (i.e., by the time __mmdrop frees the mm
490 # the lazy tlb reference of a kthread's ->active_mm (non-arch code has been
497 # mm as a lazy tlb beyond its last reference count, by shooting down these
499 # be using the mm as a lazy tlb, so that they may switch themselves to using
501 # may be using mm as a lazy tlb mm.
505 # at least all possible CPUs in which the mm is lazy.
|
| /Linux-v6.6/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-v6.6/Documentation/driver-api/driver-model/ |
| D | devres.rst | 30 that's probably because libata low level driver developers are lazy
|
| /Linux-v6.6/Documentation/powerpc/ |
| D | transactional_memory.rst | 94 Examples are glibc's getpid() and lazy symbol resolution.
|
