drew
/
acadia-newlib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
acadia-newlib/winsup/cygwin/timer.h

51 lines
1.1 KiB
C
Raw Normal View History

Cygwin: posix timers: some cleanup - use int64_t instead of long long - make is_timer_tracker const - improve copyright header comment Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-12 11:23:55 -08:00
/* timer.h: Define class timer_tracker, base class for posix timers
Cygwin: posix timers: move definition of timer_tracker class to new timer.h Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-11 10:40:03 -08:00
This file is part of Cygwin.
This software is a copyrighted work licensed under the terms of the
Cygwin license. Please consult the file "CYGWIN_LICENSE" for
details. */
#ifndef __TIMER_H__
#define __TIMER_H__
#define TT_MAGIC 0x513e4a1c
class timer_tracker
{
unsigned magic;
timer_tracker *next;
clockid_t clock_id;
sigevent evp;
timespec it_interval;
HANDLE hcancel;
HANDLE syncthread;
Cygwin: posix timers: some cleanup - use int64_t instead of long long - make is_timer_tracker const - improve copyright header comment Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-12 11:23:55 -08:00
int64_t interval_us;
int64_t sleepto_us;
Cygwin: posix timers: implement timer_getoverrun - set DELAYTIMER_MAX to INT_MAX - make sure to set siginfo_t::si_overrun, as on Linux Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-12 12:19:52 -08:00
LONG event_running;
Cygwin: timerfd: reimplement from scratch Using posix timers "timer_tracker" as base class for timerfd was flawed. Posix timers are not inherited by child processes and don't survive execve. The method used by posix timers didn't allow to share timers between processes. The timers were still per-process timers and worked entirely separate from each other. Reading from these timers via different descriptors was only synchronized within the same process. This does not reflect the timerfd semantics in Linux: The per-file timers can be dup'ed and survive fork and execve. They are still just descriptors pointing to the same timer object originally created by timerfd_create. Synchronization is performed between all descriptor instances of the same timer, system-wide. Thus, reimplement timerfd using a timer instance in shared memory, a kernel timer, and a handful of sync objects. Every process maintains a per-process timerfd struct on the cygheap maintaining a per-process thread. Every process sharing the same timerfd will run this thread checking the state of the timer, similar to the posix timer thread, just working on the shared objects and synchronizing its job with each other thread. Drop the timerfd implementation in the posix timer code and move the public API to fhandler_timerfd.c. Keep the ttstart timer_tracker anchor out of "NO_COPY" since the fixup_after_fork code should run to avoid memory leakage. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-19 10:53:48 -08:00
LONG overrun_count_curr;
Cygwin: posix timers: implement timer_getoverrun - set DELAYTIMER_MAX to INT_MAX - make sure to set siginfo_t::si_overrun, as on Linux Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-12 12:19:52 -08:00
LONG64 overrun_count;
Cygwin: posix timers: move definition of timer_tracker class to new timer.h Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-11 10:40:03 -08:00
bool cancel ();
public:
Cygwin: timerfd: reimplement from scratch Using posix timers "timer_tracker" as base class for timerfd was flawed. Posix timers are not inherited by child processes and don't survive execve. The method used by posix timers didn't allow to share timers between processes. The timers were still per-process timers and worked entirely separate from each other. Reading from these timers via different descriptors was only synchronized within the same process. This does not reflect the timerfd semantics in Linux: The per-file timers can be dup'ed and survive fork and execve. They are still just descriptors pointing to the same timer object originally created by timerfd_create. Synchronization is performed between all descriptor instances of the same timer, system-wide. Thus, reimplement timerfd using a timer instance in shared memory, a kernel timer, and a handful of sync objects. Every process maintains a per-process timerfd struct on the cygheap maintaining a per-process thread. Every process sharing the same timerfd will run this thread checking the state of the timer, similar to the posix timer thread, just working on the shared objects and synchronizing its job with each other thread. Drop the timerfd implementation in the posix timer code and move the public API to fhandler_timerfd.c. Keep the ttstart timer_tracker anchor out of "NO_COPY" since the fixup_after_fork code should run to avoid memory leakage. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-19 10:53:48 -08:00
timer_tracker (clockid_t, const sigevent *);
Cygwin: posix timers: move definition of timer_tracker class to new timer.h Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-11 10:40:03 -08:00
~timer_tracker ();
Cygwin: posix timers: some cleanup - use int64_t instead of long long - make is_timer_tracker const - improve copyright header comment Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-12 11:23:55 -08:00
inline bool is_timer_tracker () const { return magic == TT_MAGIC; }
Cygwin: posix timers: implement timer_getoverrun - set DELAYTIMER_MAX to INT_MAX - make sure to set siginfo_t::si_overrun, as on Linux Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-12 12:19:52 -08:00
inline sigevent_t *sigevt () { return &evp; }
Cygwin: timerfd: reimplement from scratch Using posix timers "timer_tracker" as base class for timerfd was flawed. Posix timers are not inherited by child processes and don't survive execve. The method used by posix timers didn't allow to share timers between processes. The timers were still per-process timers and worked entirely separate from each other. Reading from these timers via different descriptors was only synchronized within the same process. This does not reflect the timerfd semantics in Linux: The per-file timers can be dup'ed and survive fork and execve. They are still just descriptors pointing to the same timer object originally created by timerfd_create. Synchronization is performed between all descriptor instances of the same timer, system-wide. Thus, reimplement timerfd using a timer instance in shared memory, a kernel timer, and a handful of sync objects. Every process maintains a per-process timerfd struct on the cygheap maintaining a per-process thread. Every process sharing the same timerfd will run this thread checking the state of the timer, similar to the posix timer thread, just working on the shared objects and synchronizing its job with each other thread. Drop the timerfd implementation in the posix timer code and move the public API to fhandler_timerfd.c. Keep the ttstart timer_tracker anchor out of "NO_COPY" since the fixup_after_fork code should run to avoid memory leakage. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-19 10:53:48 -08:00
inline int getoverrun () const { return overrun_count_curr; }
Cygwin: posix timers: move definition of timer_tracker class to new timer.h Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-11 10:40:03 -08:00
void gettime (itimerspec *);
int settime (int, const itimerspec *, itimerspec *);
Cygwin: timerfd: reimplement from scratch Using posix timers "timer_tracker" as base class for timerfd was flawed. Posix timers are not inherited by child processes and don't survive execve. The method used by posix timers didn't allow to share timers between processes. The timers were still per-process timers and worked entirely separate from each other. Reading from these timers via different descriptors was only synchronized within the same process. This does not reflect the timerfd semantics in Linux: The per-file timers can be dup'ed and survive fork and execve. They are still just descriptors pointing to the same timer object originally created by timerfd_create. Synchronization is performed between all descriptor instances of the same timer, system-wide. Thus, reimplement timerfd using a timer instance in shared memory, a kernel timer, and a handful of sync objects. Every process maintains a per-process timerfd struct on the cygheap maintaining a per-process thread. Every process sharing the same timerfd will run this thread checking the state of the timer, similar to the posix timer thread, just working on the shared objects and synchronizing its job with each other thread. Drop the timerfd implementation in the posix timer code and move the public API to fhandler_timerfd.c. Keep the ttstart timer_tracker anchor out of "NO_COPY" since the fixup_after_fork code should run to avoid memory leakage. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-19 10:53:48 -08:00
int clean_and_unhook ();
Cygwin: posix timers: implement timer_getoverrun - set DELAYTIMER_MAX to INT_MAX - make sure to set siginfo_t::si_overrun, as on Linux Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-12 12:19:52 -08:00
LONG arm_event ();
Cygwin: timerfd: reimplement from scratch Using posix timers "timer_tracker" as base class for timerfd was flawed. Posix timers are not inherited by child processes and don't survive execve. The method used by posix timers didn't allow to share timers between processes. The timers were still per-process timers and worked entirely separate from each other. Reading from these timers via different descriptors was only synchronized within the same process. This does not reflect the timerfd semantics in Linux: The per-file timers can be dup'ed and survive fork and execve. They are still just descriptors pointing to the same timer object originally created by timerfd_create. Synchronization is performed between all descriptor instances of the same timer, system-wide. Thus, reimplement timerfd using a timer instance in shared memory, a kernel timer, and a handful of sync objects. Every process maintains a per-process timerfd struct on the cygheap maintaining a per-process thread. Every process sharing the same timerfd will run this thread checking the state of the timer, similar to the posix timer thread, just working on the shared objects and synchronizing its job with each other thread. Drop the timerfd implementation in the posix timer code and move the public API to fhandler_timerfd.c. Keep the ttstart timer_tracker anchor out of "NO_COPY" since the fixup_after_fork code should run to avoid memory leakage. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-19 10:53:48 -08:00
LONG disarm_event ();
Cygwin: posix timers: move definition of timer_tracker class to new timer.h Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-11 10:40:03 -08:00
DWORD thread_func ();
Cygwin: posix timers: convert timer_tracker::fixup_after_fork to static method Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-11 11:36:46 -08:00
static void fixup_after_fork ();
Cygwin: posix timers: move definition of timer_tracker class to new timer.h Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-11 10:40:03 -08:00
};
Cygwin: fork: move extern declarations to appropriate headers Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-16 03:59:27 -08:00
extern void fixup_timers_after_fork ();
Cygwin: posix timers: move definition of timer_tracker class to new timer.h Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2019-01-11 10:40:03 -08:00
#endif /* __TIMER_H__ */