Taylor R Campbell <riastr...@netbsd.org> writes:

>> Date: Thu, 20 Jul 2023 21:50:26 -0400
>> From: Brad Spencer <b...@samwise.nat.eldar.org>
>> 
>> With a DOMU kernel compiled with KDTRACE_HOOKS I get the following with
>> either of those dtrace probes on the DOMU:
>> 
>> dtrace -n 'sdt:xen:clock:, sdt:xen:hardclock:, sdt:xen:timecounter: { 
>> printf("%d %d %d %d %d %d %d", arg0, arg1, arg2, arg3, arg4, arg5, arg6, 
>> arg7) }'
>> dtrace: invalid probe specifier sdt:xen:clock:, sdt:xen:hardclock:, 
>> sdt:xen:timecounter: { printf("%d %d %d %d %d %d %d", arg0, arg1, arg2, 
>> arg3, arg4, arg5, arg6, arg7) }: "/usr/lib/dtrace/psinfo.d", line 46: syntax 
>> error near "u_int"
>
> Can you please file a PR about that, and pass `-x nolibs' to dtrace in
> the mean time?
>
> dtrace -x nolibs -n 'sdt:xen:clock:...'


Sorry ... ment to include this too:

The "vmstat -e | grep -e tsc -e systime -e hardclock" during the time
the system is working on doing builds:

vcpu0 missed hardclock                                       2    0 intr
vcpu1 missed hardclock                                      79    0 intr



-- 
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org

Reply via email to