Samuel Thibault f071795d80 mach: Fix bogus negative return
One can be very unlucky to call time_now first just before a second switch,
and mach_msg sleep just a bit more enough for the second time_now call to
count one second too many (or even more if scheduling is really unlucky).

So we have to protect against returning a bogus negative value in such case.
2024-08-25 03:35:29 +02:00
..
2024-08-07 11:02:03 -03:00
2024-07-14 12:44:15 +02:00
2024-08-11 15:29:56 +02:00
2024-08-07 11:02:03 -03:00
2024-06-18 10:45:36 +02:00
2024-08-07 11:02:03 -03:00
2024-07-08 21:51:03 +02:00
2024-08-25 03:35:29 +02:00
2024-06-17 13:47:09 +00:00
2024-08-08 14:53:53 +02:00
2024-06-17 13:47:09 +00:00
2024-04-10 14:53:39 -03:00
2024-08-08 14:53:55 +02:00
2024-08-08 13:01:02 +02:00
2024-08-07 11:02:03 -03:00