| /Linux-v5.4/kernel/ |
| D | irq_work.c | 127 struct llist_head *raised, *lazy; in irq_work_needs_cpu() local
130 lazy = this_cpu_ptr(&lazy_list); in irq_work_needs_cpu()
133 if (llist_empty(lazy)) in irq_work_needs_cpu()
|
| /Linux-v5.4/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_irq.c | 160 bool lazy, in vmw_fallback_wait() argument
205 if (lazy) in vmw_fallback_wait()
286 bool lazy, uint32_t seqno, in vmw_wait_seqno() argument
301 return vmw_fallback_wait(dev_priv, lazy, true, seqno, in vmw_wait_seqno()
305 return vmw_fallback_wait(dev_priv, lazy, false, seqno, in vmw_wait_seqno()
|
| D | vmwgfx_fence.h | 94 bool lazy,
|
| D | vmwgfx_fence.c | 525 int vmw_fence_obj_wait(struct vmw_fence_obj *fence, bool lazy, in vmw_fence_obj_wait() argument
840 ret = vmw_fence_obj_wait(fence, arg->lazy, true, timeout); in vmw_fence_obj_wait_ioctl()
|
| D | vmwgfx_drv.h | 1020 extern int vmw_wait_seqno(struct vmw_private *dev_priv, bool lazy,
1028 bool lazy,
|
| /Linux-v5.4/kernel/rcu/ |
| D | rcu_segcblist.h | 109 struct rcu_head *rhp, bool lazy);
111 struct rcu_head *rhp, bool lazy);
|
| D | rcu_segcblist.c | 256 struct rcu_head *rhp, bool lazy) in rcu_segcblist_enqueue() argument
259 if (lazy) in rcu_segcblist_enqueue()
278 struct rcu_head *rhp, bool lazy) in rcu_segcblist_entrain() argument
285 if (lazy) in rcu_segcblist_entrain()
|
| D | tree.c | 2555 __call_rcu(struct rcu_head *head, rcu_callback_t func, bool lazy) in __call_rcu() argument
2593 rcu_segcblist_enqueue(&rdp->cblist, head, lazy); in __call_rcu()
|
| /Linux-v5.4/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-v5.4/drivers/staging/exfat/ |
| D | TODO | 8 That doesn't look right. How did it ever work? Are they relying on lazy
|
| /Linux-v5.4/drivers/gpu/drm/nouveau/ |
| D | nouveau_fence.h | 26 int nouveau_fence_wait(struct nouveau_fence *, bool lazy, bool intr);
|
| D | nouveau_fence.c | 316 nouveau_fence_wait(struct nouveau_fence *fence, bool lazy, bool intr) in nouveau_fence_wait() argument
320 if (!lazy) in nouveau_fence_wait()
|
| /Linux-v5.4/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-v5.4/arch/nds32/ |
| D | Kconfig.cpu | 22 bool "lazy FPU support"
26 Say Y here to enable the lazy FPU scheme. The lazy FPU scheme can
|
| /Linux-v5.4/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 targ…
|
| /Linux-v5.4/include/uapi/drm/ |
| D | vmwgfx_drm.h | 630 __s32 lazy; member
|
| /Linux-v5.4/arch/arm/vfp/ |
| D | vfphw.S | 81 ldr r3, [sp, #S_PSR] @ Neither lazy restore nor FP exceptions
|
| /Linux-v5.4/Documentation/RCU/ |
| D | stallwarn.txt | 233 rcu_prepare_for_idle(). The "Nonlazy posted:" indicates lazy-callback
234 status, so that an "l" indicates that all callbacks were lazy at the start
236 no non-lazy callbacks (in both cases, "." is printed otherwise, as
|
| /Linux-v5.4/Documentation/parisc/ |
| D | registers.rst | 18 CR10 (CCR) lazy FPU saving*
|
| /Linux-v5.4/arch/x86/include/asm/ |
| D | hyperv-tlfs.h | 774 u64 lazy:1; member
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | fuse.txt | 25 umounted. Note that detaching (or lazy umounting) the filesystem
213 filesystem is still attached (it hasn't been lazy unmounted)
|
| D | autofs-mount-control.txt | 21 Currently autofs uses "umount -l" (lazy umount) to clear active mounts
22 at restart. While using lazy umount works for most cases, anything that
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | devres.rst | 30 that's probably because libata low level driver developers are lazy
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | transactional_memory.rst | 94 Examples are glibc's getpid() and lazy symbol resolution.
|
| /Linux-v5.4/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
|
