Home
last modified time | relevance | path

Searched refs:firing (Results 1 – 7 of 7) sorted by relevance

/Linux-v4.19/kernel/time/
Dposix-cpu-timers.c392 if (timer->it.cpu.firing) in posix_cpu_timer_del()
611 if (unlikely(timer->it.cpu.firing)) { in posix_cpu_timer_set()
612 timer->it.cpu.firing = -1; in posix_cpu_timer_set()
774 struct list_head *firing, in check_timers_list() argument
787 t->firing = 1; in check_timers_list()
788 list_move_tail(&t->entry, firing); in check_timers_list()
808 struct list_head *firing) in check_thread_timers() argument
825 expires = check_timers_list(timers, firing, prof_ticks(tsk)); in check_thread_timers()
828 expires = check_timers_list(++timers, firing, virt_ticks(tsk)); in check_thread_timers()
831 tsk_expires->sched_exp = check_timers_list(++timers, firing, in check_thread_timers()
[all …]
/Linux-v4.19/include/linux/
Dposix-timers.h17 int firing; member
/Linux-v4.19/Documentation/scsi/
DChangeLog.megaraid_sas557 v. If FW in operational state before firing INIT, now we send RESET Flag to FW instead of just READ…
575 ii. Bug fix : Disable controller interrupt before firing INIT cmd to FW.
/Linux-v4.19/drivers/xen/
DKconfig103 firing.
/Linux-v4.19/Documentation/
Dkprobes.txt657 probepoint repeatedly, firing a simple handler each time, reports 1-2
/Linux-v4.19/Documentation/virtual/kvm/
Dtimekeeping.txt571 Since scheduling may be based on precise timing and firing of interrupts, the
/Linux-v4.19/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt4137 figuring out what its pid is, firing up gdb, and attaching it to that