Searched hist:"52 d500e5b4abc36a9c2106de52412da5324ca9ee" (Results 1 – 4 of 4) sorted by relevance
/haiku/headers/private/kernel/ |
H A D | UserTimer.h | 52d500e5b4abc36a9c2106de52412da5324ca9ee Tue Oct 28 22:37:30 UTC 2014 Michael Lotz <mmlr@mlotz.ch> kernel: Workaround for double lock of spinlock in user timers.
The thread that is being [un]scheduled already has its time_lock locked in {stop|continue}_cpu_timers(). When updating the TeamTimeUserTimer, the team is asked for its cpu time. Team::CPUTime() then iterates the threads of the team and locks the time_lock of the thread again.
This workaround passes a possibly locked thread through the relevant functions so Team::CPUTime() can decide whether or not a thread it iterates needs to be locked or not.
This works around #11032 and its duplicates #11314 and #11344.
|
H A D | thread_types.h | 52d500e5b4abc36a9c2106de52412da5324ca9ee Tue Oct 28 22:37:30 UTC 2014 Michael Lotz <mmlr@mlotz.ch> kernel: Workaround for double lock of spinlock in user timers.
The thread that is being [un]scheduled already has its time_lock locked in {stop|continue}_cpu_timers(). When updating the TeamTimeUserTimer, the team is asked for its cpu time. Team::CPUTime() then iterates the threads of the team and locks the time_lock of the thread again.
This workaround passes a possibly locked thread through the relevant functions so Team::CPUTime() can decide whether or not a thread it iterates needs to be locked or not.
This works around #11032 and its duplicates #11314 and #11344.
|
/haiku/src/system/kernel/ |
H A D | UserTimer.cpp | 52d500e5b4abc36a9c2106de52412da5324ca9ee Tue Oct 28 22:37:30 UTC 2014 Michael Lotz <mmlr@mlotz.ch> kernel: Workaround for double lock of spinlock in user timers.
The thread that is being [un]scheduled already has its time_lock locked in {stop|continue}_cpu_timers(). When updating the TeamTimeUserTimer, the team is asked for its cpu time. Team::CPUTime() then iterates the threads of the team and locks the time_lock of the thread again.
This workaround passes a possibly locked thread through the relevant functions so Team::CPUTime() can decide whether or not a thread it iterates needs to be locked or not.
This works around #11032 and its duplicates #11314 and #11344.
|
H A D | team.cpp | 52d500e5b4abc36a9c2106de52412da5324ca9ee Tue Oct 28 22:37:30 UTC 2014 Michael Lotz <mmlr@mlotz.ch> kernel: Workaround for double lock of spinlock in user timers.
The thread that is being [un]scheduled already has its time_lock locked in {stop|continue}_cpu_timers(). When updating the TeamTimeUserTimer, the team is asked for its cpu time. Team::CPUTime() then iterates the threads of the team and locks the time_lock of the thread again.
This workaround passes a possibly locked thread through the relevant functions so Team::CPUTime() can decide whether or not a thread it iterates needs to be locked or not.
This works around #11032 and its duplicates #11314 and #11344.
|