Home
last modified time | relevance | path

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

/linux-6.15/kernel/time/
H A Dposix-cpu-timers.c496 if (timer->it.cpu.firing) { in posix_cpu_timer_del()
503 timer->it.cpu.firing = false; in posix_cpu_timer_del()
675 timer->it.cpu.firing = false; in posix_cpu_timer_set()
816 ctmr->firing = true; in collect_timerqueue()
827 struct list_head *firing) in collect_posix_cputimers() argument
866 struct list_head *firing) in check_thread_timers() argument
943 struct list_head *firing) in check_process_timers() argument
1299 LIST_HEAD(firing); in handle_posix_cpu_timers()
1318 check_thread_timers(tsk, &firing); in handle_posix_cpu_timers()
1382 cpu_firing = timer->it.cpu.firing; in handle_posix_cpu_timers()
[all …]
/linux-6.15/include/linux/
H A Dposix-timers.h59 bool firing; member
/linux-6.15/Documentation/scsi/
H 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-6.15/drivers/xen/
H A DKconfig89 firing.
/linux-6.15/Documentation/networking/dsa/
H A Dsja1105.rst279 firing at the same time does not apply because there is a single schedule in
/linux-6.15/Documentation/virt/kvm/x86/
H A Dtimekeeping.rst601 Since scheduling may be based on precise timing and firing of interrupts, the
/linux-6.15/Documentation/trace/
H A Dkprobes.rst645 probepoint repeatedly, firing a simple handler each time, reports 1-2
/linux-6.15/Documentation/driver-api/gpio/
H A Ddriver.rst121 reasons. This can result in the value being unstable or irqs firing repeatedly