Home
last modified time | relevance | path

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

/linux-6.6.21/kernel/time/
Dposix-cpu-timers.c496 if (timer->it.cpu.firing) in posix_cpu_timer_del()
671 if (unlikely(timer->it.cpu.firing)) { in posix_cpu_timer_set()
672 timer->it.cpu.firing = -1; in posix_cpu_timer_set()
833 struct list_head *firing, u64 now) in collect_timerqueue() argument
848 ctmr->firing = 1; in collect_timerqueue()
852 list_add_tail(&ctmr->elist, firing); in collect_timerqueue()
859 struct list_head *firing) in collect_posix_cputimers() argument
865 base->nextevt = collect_timerqueue(&base->tqhead, firing, in collect_posix_cputimers()
898 struct list_head *firing) in check_thread_timers() argument
911 collect_posix_cputimers(pct, samples, firing); in check_thread_timers()
[all …]
/linux-6.6.21/include/linux/
Dposix-timers.h76 int firing; member
/linux-6.6.21/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-6.6.21/drivers/xen/
DKconfig89 firing.
/linux-6.6.21/Documentation/networking/dsa/
Dsja1105.rst279 firing at the same time does not apply because there is a single schedule in
/linux-6.6.21/Documentation/virt/kvm/x86/
Dtimekeeping.rst601 Since scheduling may be based on precise timing and firing of interrupts, the
/linux-6.6.21/Documentation/trace/
Dkprobes.rst644 probepoint repeatedly, firing a simple handler each time, reports 1-2
/linux-6.6.21/Documentation/driver-api/gpio/
Ddriver.rst122 reasons. This can result in the value being unstable or irqs firing repeatedly