Fabian Keil wrote:
> At least on my system, timestamp offsets can only can be relied
> on with either kern.timecounter.hardware=TSC or with C3
> states disabled, though.
>
> Measuring the elapsed time (in ms) between events that happen
> in roughly 1 second intervals with kern.timecounter.hardwa
On Sun, Aug 21, 2011 at 7:05 AM, Fabian Keil
wrote:
>
> Ashley Williams wrote:
>
> > walltimestamp and timestamp don't appear to be right in BETA-1:
> >
> >
> > # dtrace -qn 'syscall::exec*:return { printf("%Y
> > %s\n",walltimestamp,curpsinfo->pr_psargs); }'
> > 1970 Jan 1 10:00:00 date
> > 197
Ashley Williams wrote:
> walltimestamp and timestamp don't appear to be right in BETA-1:
>
>
> # dtrace -qn 'syscall::exec*:return { printf("%Y
> %s\n",walltimestamp,curpsinfo->pr_psargs); }'
> 1970 Jan 1 10:00:00 date
> 1970 Jan 1 10:00:00 ping
> 1970 Jan 1 10:00:00 ls
I can reproduce this
walltimestamp and timestamp don't appear to be right in BETA-1:
# dtrace -qn 'syscall::exec*:return { printf("%Y
%s\n",walltimestamp,curpsinfo->pr_psargs); }'
1970 Jan 1 10:00:00 date
1970 Jan 1 10:00:00 ping
1970 Jan 1 10:00:00 ls
# dtrace -qn 'syscall::exec*:return { printf("%Y
%s\n",times
