Home
last modified time | relevance | path

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

/linux/kernel/time/
A Dposix-cpu-timers.c497 if (timer->it.cpu.firing) in posix_cpu_timer_del()
670 timer->it.cpu.firing = -1; in posix_cpu_timer_set()
811 ctmr->firing = 1; in collect_timerqueue()
822 struct list_head *firing) in collect_posix_cputimers() argument
861 struct list_head *firing) in check_thread_timers() argument
938 struct list_head *firing) in check_process_timers() argument
1294 LIST_HEAD(firing); in handle_posix_cpu_timers()
1313 check_thread_timers(tsk, &firing); in handle_posix_cpu_timers()
1315 check_process_timers(tsk, &firing); in handle_posix_cpu_timers()
1377 cpu_firing = timer->it.cpu.firing; in handle_posix_cpu_timers()
[all …]
/linux/include/linux/
A Dposix-timers.h52 int firing; member
/linux/Documentation/scsi/
A 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/drivers/xen/
A DKconfig89 firing.
/linux/Documentation/networking/dsa/
A Dsja1105.rst279 firing at the same time does not apply because there is a single schedule in
/linux/Documentation/trace/
A Dkprobes.rst645 probepoint repeatedly, firing a simple handler each time, reports 1-2
/linux/Documentation/virt/kvm/x86/
A Dtimekeeping.rst601 Since scheduling may be based on precise timing and firing of interrupts, the
/linux/Documentation/driver-api/gpio/
A Ddriver.rst121 reasons. This can result in the value being unstable or irqs firing repeatedly

Completed in 15 milliseconds