Home
last modified time | relevance | path

Searched refs:lazy (Results 1 – 25 of 35) sorted by relevance

12

/kernel/linux/linux-5.10/kernel/
Dirq_work.c118 struct llist_head *raised, *lazy; in irq_work_needs_cpu() local
121 lazy = this_cpu_ptr(&lazy_list); in irq_work_needs_cpu()
124 if (llist_empty(lazy)) in irq_work_needs_cpu()
/kernel/linux/linux-5.10/drivers/gpu/drm/vmwgfx/
Dvmwgfx_irq.c160 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()
Dvmwgfx_fence.h94 bool lazy,
Dvmwgfx_fence.c525 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()
Dvmwgfx_drv.h1105 extern int vmw_wait_seqno(struct vmw_private *dev_priv, bool lazy,
1113 bool lazy,
/kernel/linux/linux-5.10/Documentation/vm/
Dactive_mm.rst59 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
/kernel/linux/linux-5.10/Documentation/arm/
Dkernel_mode_neon.rst30 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
/kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/
Dnouveau_fence.h26 int nouveau_fence_wait(struct nouveau_fence *, bool lazy, bool intr);
Dnouveau_fence.c325 nouveau_fence_wait(struct nouveau_fence *fence, bool lazy, bool intr) in nouveau_fence_wait() argument
329 if (!lazy) in nouveau_fence_wait()
/kernel/linux/linux-5.10/arch/nds32/
DKconfig.cpu22 bool "lazy FPU support"
26 Say Y here to enable the lazy FPU scheme. The lazy FPU scheme can
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dperf-probe.txt165 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…
/kernel/linux/linux-5.10/include/asm-generic/
Dhyperv-tlfs.h280 u64 lazy:1; member
/kernel/linux/patches/linux-5.10/prebuilts/usr/include/drm/
Dvmwgfx_drm.h202 __s32 lazy; member
/kernel/linux/patches/linux-4.19/prebuilts/usr/include/drm/
Dvmwgfx_drm.h187 __s32 lazy; member
/kernel/linux/linux-5.10/include/uapi/drm/
Dvmwgfx_drm.h635 __s32 lazy; member
/kernel/linux/linux-5.10/Documentation/parisc/
Dregisters.rst18 CR10 (CCR) lazy FPU saving*
/kernel/linux/linux-5.10/Documentation/filesystems/
Dfuse.rst27 umounted. Note that detaching (or lazy umounting) the filesystem
199 filesystem is still attached (it hasn't been lazy unmounted)
Dautofs-mount-control.rst23 Currently autofs uses "umount -l" (lazy umount) to clear active mounts
24 at restart. While using lazy umount works for most cases, anything that
/kernel/linux/linux-5.10/Documentation/driver-api/driver-model/
Ddevres.rst30 that's probably because libata low level driver developers are lazy
/kernel/linux/linux-5.10/arch/arm/crypto/
Dpoly1305-core.S_shipped522 @ lazy reduction as discussed in "NEON crypto" by D.J. Bernstein
930 @ lazy reduction interleaved with base 2^32 -> base 2^26 of
1100 @ lazy reduction, but without narrowing
/kernel/linux/linux-5.10/arch/arm64/crypto/
Dpoly1305-core.S_shipped639 // lazy reduction as discussed in "NEON crypto" by D.J. Bernstein
784 // lazy reduction, but without narrowing
/kernel/linux/linux-5.10/Documentation/powerpc/
Dtransactional_memory.rst94 Examples are glibc's getpid() and lazy symbol resolution.
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/
Dnuma_memory_policy.rst140 support allocation at fault time--a.k.a lazy allocation--so hugetlbfs
142 Although hugetlbfs segments now support lazy allocation, their support
/kernel/linux/linux-5.10/arch/sparc/lib/
Dchecksum_32.S421 addx %g5, %g0, %g5 ! I am now to lazy to optimize this (question it
/kernel/linux/linux-5.10/Documentation/locking/
Dww-mutex-design.rst350 The Wound-Wait preemption is implemented with a lazy-preemption scheme:

12