Searched hist:bb53dd56c30c6360fc82be762ed98b0af6b9f69f (Results 1 – 3 of 3) sorted by relevance
| /freebsd/lib/libkvm/ |
| H A D | kvm_proc.c | diff bb53dd56c30c6360fc82be762ed98b0af6b9f69f Mon Mar 21 14:33:11 CET 2022 firk <firk@cantconnect.ru> kern_tc.c/cputick2usec() (which is used to calculate cputime from
cpu ticks) has some imprecision and, worse, huge timestep (about
20 minutes on 4GHz CPU) near 53.4 days of elapsed time.
kern_time.c/cputick2timespec() (it is used for clock_gettime() for
querying process or thread consumed cpu time) Uses cputick2usec()
and then needlessly converting usec to nsec, obviously losing
precision even with fixed cputick2usec().
kern_time.c/kern_clock_getres() uses some weird (anyway wrong)
formula for getting cputick resolution.
PR: 262215
Reviewed by: gnn
Differential Revision: https://reviews.freebsd.org/D34558
|
| /freebsd/sys/kern/ |
| H A D | kern_time.c | diff bb53dd56c30c6360fc82be762ed98b0af6b9f69f Mon Mar 21 14:33:11 CET 2022 firk <firk@cantconnect.ru> kern_tc.c/cputick2usec() (which is used to calculate cputime from
cpu ticks) has some imprecision and, worse, huge timestep (about
20 minutes on 4GHz CPU) near 53.4 days of elapsed time.
kern_time.c/cputick2timespec() (it is used for clock_gettime() for
querying process or thread consumed cpu time) Uses cputick2usec()
and then needlessly converting usec to nsec, obviously losing
precision even with fixed cputick2usec().
kern_time.c/kern_clock_getres() uses some weird (anyway wrong)
formula for getting cputick resolution.
PR: 262215
Reviewed by: gnn
Differential Revision: https://reviews.freebsd.org/D34558
|
| H A D | kern_tc.c | diff bb53dd56c30c6360fc82be762ed98b0af6b9f69f Mon Mar 21 14:33:11 CET 2022 firk <firk@cantconnect.ru> kern_tc.c/cputick2usec() (which is used to calculate cputime from
cpu ticks) has some imprecision and, worse, huge timestep (about
20 minutes on 4GHz CPU) near 53.4 days of elapsed time.
kern_time.c/cputick2timespec() (it is used for clock_gettime() for
querying process or thread consumed cpu time) Uses cputick2usec()
and then needlessly converting usec to nsec, obviously losing
precision even with fixed cputick2usec().
kern_time.c/kern_clock_getres() uses some weird (anyway wrong)
formula for getting cputick resolution.
PR: 262215
Reviewed by: gnn
Differential Revision: https://reviews.freebsd.org/D34558
|