Home
last modified time | relevance | path

Searched full:observing (Results 1 – 25 of 35) sorted by relevance

12

/linux/Documentation/ABI/testing/
H A Dsysfs-class-led-trigger-usbport9 observing them for any connected devices and lighting on LED if
/linux/tools/testing/selftests/drivers/net/mlxsw/
H A Dtc_police_occ.sh5 # counted by observing policers' occupancy via devlink-resource.
H A Dport_range_occ.sh6 # observing port range registers' occupancy via devlink-resource.
/linux/Documentation/devicetree/bindings/soc/fsl/
H A Dfsl,qman-fqd.yaml30 The size of the FQD and PFDP must be chosen by observing the hardware features
/linux/tools/testing/selftests/arm64/fp/
H A DREADME67 To try to reproduce the bugs that we have been observing, sve-stress
/linux/tools/kvm/kvm_stat/
H A Dkvm_stat.txt18 This tool is useful for observing guest behavior from the host perspective.
/linux/tools/perf/util/
H A Dsideband_evlist.c44 * that we're observing when, for instance, reading the build-ids at in perf_evlist__poll_thread()
/linux/arch/mips/include/asm/
H A Dfpu_emulator.h177 * Mask the FCSR Cause bits according to the Enable bits, observing
/linux/arch/loongarch/include/asm/
H A Dfpu.h60 * Mask the FCSR Cause bits according to the Enable bits, observing
/linux/mm/
H A Dmmap_lock.c116 * back the vm_refcnt. That is a narrow window for observing a raised in vma_mark_detached()
/linux/Documentation/trace/
H A Dosnoise-tracer.rst25 the latency. The hwlat detects the NMI execution by observing
/linux/Documentation/virt/kvm/
H A Dvcpu-requests.rst207 can exclude the possibility of a VCPU thread observing
/linux/drivers/platform/surface/
H A Dsurface3_power.c30 * . the various registers semantic as been deduced by observing the register
/linux/drivers/net/wireless/zydas/zd1211rw/
H A Dzd_rf_uw2453.c79 * table a little by observing that both channels in a consecutive pair share
/linux/include/xen/interface/
H A Dgrant_table.h58 * for this to occur (detect by observing GTF_transfer_completed in
/linux/fs/notify/
H A Dfsnotify.c164 * d_lock is a sufficient barrier to prevent observing a non-watched in fsnotify_clear_child_dentry_flag()
/linux/kernel/irq/
H A Dirqdesc.c1004 * interrupt descriptor is observing an rcu grace period before
/linux/arch/x86/kernel/cpu/resctrl/
H A Dcore.c34 * read-side critical section, to avoid observing concurrent modification.
/linux/arch/arm64/
H A DKconfig2049 accessing the counter registers. Even if you are not observing these
2268 booting the kernel. If unsure and you are not observing these
/linux/arch/powerpc/kernel/
H A Dhead_64.S123 * observing the alignment requirement.
/linux/crypto/
H A Djitterentropy.c164 * necessarily have been observed, so there is no chance of observing 0 of these
/linux/include/linux/
H A Dmaple_tree.h278 * necessarily obvious. Usually, this is done by observing that pointers are
/linux/drivers/gpu/drm/
H A Ddrm_framebuffer.c1134 * Since we're holding a reference ourselves, observing a refcount of 1 in drm_framebuffer_remove()
/linux/kernel/kcsan/
H A Dcore.c612 * Delay this thread, to increase probability of observing a racy in kcsan_setup_watchpoint()
/linux/drivers/edac/
H A Di10nm_base.c767 * By observing that the MMIO registers of these absent in i10nm_imc_absent()

12