Searched hist:d8fcc8a82519cef977c689cee497316be6f1531f (Results 1 – 5 of 5) sorted by relevance
| /haiku/src/system/kernel/ |
| H A D | UserTimer.cpp | d8fcc8a82519cef977c689cee497316be6f1531f Thu Oct 31 00:49:43 UTC 2013 Pawel Dziepak <pdziepak@quarnos.org> kernel: Remove B_TIMER_ACQUIRE_SCHEDULER_LOCK flag
The flag main purpose is to avoid race conditions between event handler
and cancel_timer(). However, cancel_timer() is safe even without
using gSchedulerLock.
If the event is scheduled to happen on other CPU than the CPU that
invokes cancel_timer() then cancel_timer() either disables the event
before its handler starts executing or waits until the event handler
is done.
If the event is scheduled on the same CPU that calls cancel_timer()
then, since cancel_timer() disables interrupts, the event is either
executed before cancel_timer() or when the timer interrupt handler
starts running the event is already disabled.
|
| H A D | timer.cpp | d8fcc8a82519cef977c689cee497316be6f1531f Thu Oct 31 00:49:43 UTC 2013 Pawel Dziepak <pdziepak@quarnos.org> kernel: Remove B_TIMER_ACQUIRE_SCHEDULER_LOCK flag
The flag main purpose is to avoid race conditions between event handler
and cancel_timer(). However, cancel_timer() is safe even without
using gSchedulerLock.
If the event is scheduled to happen on other CPU than the CPU that
invokes cancel_timer() then cancel_timer() either disables the event
before its handler starts executing or waits until the event handler
is done.
If the event is scheduled on the same CPU that calls cancel_timer()
then, since cancel_timer() disables interrupts, the event is either
executed before cancel_timer() or when the timer interrupt handler
starts running the event is already disabled.
|
| H A D | thread.cpp | d8fcc8a82519cef977c689cee497316be6f1531f Thu Oct 31 00:49:43 UTC 2013 Pawel Dziepak <pdziepak@quarnos.org> kernel: Remove B_TIMER_ACQUIRE_SCHEDULER_LOCK flag
The flag main purpose is to avoid race conditions between event handler
and cancel_timer(). However, cancel_timer() is safe even without
using gSchedulerLock.
If the event is scheduled to happen on other CPU than the CPU that
invokes cancel_timer() then cancel_timer() either disables the event
before its handler starts executing or waits until the event handler
is done.
If the event is scheduled on the same CPU that calls cancel_timer()
then, since cancel_timer() disables interrupts, the event is either
executed before cancel_timer() or when the timer interrupt handler
starts running the event is already disabled.
|
| /haiku/headers/private/kernel/ |
| H A D | timer.h | d8fcc8a82519cef977c689cee497316be6f1531f Thu Oct 31 00:49:43 UTC 2013 Pawel Dziepak <pdziepak@quarnos.org> kernel: Remove B_TIMER_ACQUIRE_SCHEDULER_LOCK flag
The flag main purpose is to avoid race conditions between event handler
and cancel_timer(). However, cancel_timer() is safe even without
using gSchedulerLock.
If the event is scheduled to happen on other CPU than the CPU that
invokes cancel_timer() then cancel_timer() either disables the event
before its handler starts executing or waits until the event handler
is done.
If the event is scheduled on the same CPU that calls cancel_timer()
then, since cancel_timer() disables interrupts, the event is either
executed before cancel_timer() or when the timer interrupt handler
starts running the event is already disabled.
|
| /haiku/src/system/kernel/scheduler/ |
| H A D | scheduler.cpp | d8fcc8a82519cef977c689cee497316be6f1531f Thu Oct 31 00:49:43 UTC 2013 Pawel Dziepak <pdziepak@quarnos.org> kernel: Remove B_TIMER_ACQUIRE_SCHEDULER_LOCK flag
The flag main purpose is to avoid race conditions between event handler
and cancel_timer(). However, cancel_timer() is safe even without
using gSchedulerLock.
If the event is scheduled to happen on other CPU than the CPU that
invokes cancel_timer() then cancel_timer() either disables the event
before its handler starts executing or waits until the event handler
is done.
If the event is scheduled on the same CPU that calls cancel_timer()
then, since cancel_timer() disables interrupts, the event is either
executed before cancel_timer() or when the timer interrupt handler
starts running the event is already disabled.
|