You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(jailer): account time spent in the jailer more accurately
After da92bf6, the CPU time we got from get_time_us was much shorter,
and that caused an underflow when calculating the jailer_cpu_time_us.
That resulted in Firecracker getting called with a huge value for
`--parent-cpu-time`.
Before this fix:
/firecracker [...] --parent-cpu-time-us 18446744073709551368
After this fix:
/firecracker [...] --parent-cpu-time-us 4375
The new time is higher than before da92bf6, because a) that commit
introduced a fork, which carries some overhead, and b) we now account
for CPU time during forks.
Fixes: da92bf6
Signed-off-by: Pablo Barbáchano <[email protected]>
0 commit comments