xref: /freebsd/share/man/man9/ktr.9 (revision a1382e7fd264dfd7315438a1359ead7fcddd9354)
1a1382e7fSJohn Baldwin.\" Copyright (c) 2001 John H. Baldwin <jhb@FreeBSD.org>
2a1382e7fSJohn Baldwin.\" All rights reserved.
3a1382e7fSJohn Baldwin.\"
4a1382e7fSJohn Baldwin.\" Redistribution and use in source and binary forms, with or without
5a1382e7fSJohn Baldwin.\" modification, are permitted provided that the following conditions
6a1382e7fSJohn Baldwin.\" are met:
7a1382e7fSJohn Baldwin.\" 1. Redistributions of source code must retain the above copyright
8a1382e7fSJohn Baldwin.\"    notice, this list of conditions and the following disclaimer.
9a1382e7fSJohn Baldwin.\" 2. Redistributions in binary form must reproduce the above copyright
10a1382e7fSJohn Baldwin.\"    notice, this list of conditions and the following disclaimer in the
11a1382e7fSJohn Baldwin.\"    documentation and/or other materials provided with the distribution.
12a1382e7fSJohn Baldwin.\"
13a1382e7fSJohn Baldwin.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
14a1382e7fSJohn Baldwin.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15a1382e7fSJohn Baldwin.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16a1382e7fSJohn Baldwin.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
17a1382e7fSJohn Baldwin.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18a1382e7fSJohn Baldwin.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19a1382e7fSJohn Baldwin.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20a1382e7fSJohn Baldwin.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21a1382e7fSJohn Baldwin.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22a1382e7fSJohn Baldwin.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
23a1382e7fSJohn Baldwin.\" SUCH DAMAGE.
24a1382e7fSJohn Baldwin.\"
25a1382e7fSJohn Baldwin.\" $FreeBSD$
26a1382e7fSJohn Baldwin.\"
27a1382e7fSJohn Baldwin.Dd February 15, 2001
28a1382e7fSJohn Baldwin.Dt KTR 9
29a1382e7fSJohn Baldwin.Os
30a1382e7fSJohn Baldwin.Sh NAME
31a1382e7fSJohn Baldwin.Nm CTR0 ,
32a1382e7fSJohn Baldwin.Nm CTR1 ,
33a1382e7fSJohn Baldwin.Nm CTR2 ,
34a1382e7fSJohn Baldwin.Nm CTR3 ,
35a1382e7fSJohn Baldwin.Nm CTR4 ,
36a1382e7fSJohn Baldwin.Nm CTR5
37a1382e7fSJohn Baldwin.Nd kernel tracing facility
38a1382e7fSJohn Baldwin.Sh SYNOPSIS
39a1382e7fSJohn Baldwin.Fd #include <sys/ktr.h>
40a1382e7fSJohn Baldwin.Vt "extern	int ktr_cpumask" ;
41a1382e7fSJohn Baldwin.Vt "extern	int ktr_entries" ;
42a1382e7fSJohn Baldwin.Vt "extern	int ktr_extend" ;
43a1382e7fSJohn Baldwin.Vt "extern	int ktr_mask" ;
44a1382e7fSJohn Baldwin.Vt "extern	int ktr_verbose" ;
45a1382e7fSJohn Baldwin.Vt "extern	struct ktr_entry ktr_buf[]" ;
46a1382e7fSJohn Baldwin.Ft void
47a1382e7fSJohn Baldwin.Fn CTR0 "u_int mask" "char *format"
48a1382e7fSJohn Baldwin.Ft void
49a1382e7fSJohn Baldwin.Fn CTR1 "u_int mask" "char *format" "arg1"
50a1382e7fSJohn Baldwin.Ft void
51a1382e7fSJohn Baldwin.Fn CTR2 "u_int mask" "char *format" "arg1" "arg2"
52a1382e7fSJohn Baldwin.Ft void
53a1382e7fSJohn Baldwin.Fn CTR3 "u_int mask" "char *format" "arg1" "arg2" "arg3"
54a1382e7fSJohn Baldwin.Ft void
55a1382e7fSJohn Baldwin.Fn CTR4 "u_int mask" "char *format" "arg1" "arg2" "arg3" "arg4"
56a1382e7fSJohn Baldwin.Ft void
57a1382e7fSJohn Baldwin.Fn CTR5 "u_int mask" "char *format" "arg1" "arg2" "arg3" "arg4" "arg5"
58a1382e7fSJohn Baldwin.Sh DESCRIPTION
59a1382e7fSJohn BaldwinKTR provides a circular buffer of events that can be logged in a printf style
60a1382e7fSJohn Baldwinfashion.
61a1382e7fSJohn BaldwinThese events can then be dumped either via
62a1382e7fSJohn Baldwin.Xr ddb 4
63a1382e7fSJohn Baldwinor
64a1382e7fSJohn Baldwin.Xr gdb 1 .
65a1382e7fSJohn Baldwin.Pp
66a1382e7fSJohn BaldwinEvents are created and logged in the kernel via the
67a1382e7fSJohn Baldwin.Dv CTRx
68a1382e7fSJohn Baldwinmacros.
69a1382e7fSJohn BaldwinThe first parameter is a mask of event types
70a1382e7fSJohn Baldwin.Pq Dv KTR_*
71a1382e7fSJohn Baldwindefined in
72a1382e7fSJohn Baldwin.Aq Pa sys/ktr.h .
73a1382e7fSJohn BaldwinThe event will be logged only if any of the event types specified in
74a1382e7fSJohn Baldwin.Fa mask
75a1382e7fSJohn Baldwinare enabled in the global event mask stored in
76a1382e7fSJohn Baldwin.Va ktr_mask .
77a1382e7fSJohn BaldwinThe
78a1382e7fSJohn Baldwin.Fa format
79a1382e7fSJohn Baldwinargument is a
80a1382e7fSJohn Baldwin.Xr printf 9
81a1382e7fSJohn Baldwinstyle format string used to build the text of the event log message.
82a1382e7fSJohn BaldwinFollowing the
83a1382e7fSJohn Baldwin.Fa format
84a1382e7fSJohn Baldwinstring are zero to five arguments referenced by
85a1382e7fSJohn Baldwin.Fa format .
86a1382e7fSJohn BaldwinNote that the different macros differ only in the number of arguments each
87a1382e7fSJohn Baldwinone takes, as indicated by its name.
88a1382e7fSJohn BaldwinEach event is logged with a timestamp in addition to the log message.
89a1382e7fSJohn Baldwin.Pp
90a1382e7fSJohn BaldwinThe
91a1382e7fSJohn Baldwin.Va ktr_entries
92a1382e7fSJohn Baldwinvariable contains the number of entries in the
93a1382e7fSJohn Baldwin.Va ktr_buf
94a1382e7fSJohn Baldwinarray.
95a1382e7fSJohn BaldwinThese variables are mostly useful for post-mortem crash dump tools to locate
96a1382e7fSJohn Baldwinthe base of the circular trace buffer and its length.
97a1382e7fSJohn Baldwin.Pp
98a1382e7fSJohn BaldwinThe
99a1382e7fSJohn Baldwin.Va ktr_mask
100a1382e7fSJohn Baldwinvariable contains the run time mask of events to log.
101a1382e7fSJohn Baldwin.Pp
102a1382e7fSJohn BaldwinThe kernel can be configured to compile with several extensions to the base
103a1382e7fSJohn Baldwinfunctionality.
104a1382e7fSJohn BaldwinThese extensions can be checked for at runtime via the
105a1382e7fSJohn Baldwin.Va ktr_extend
106a1382e7fSJohn Baldwinvariable.
107a1382e7fSJohn BaldwinIt will be set to zero if the extensions are not compiled in and non-zero
108a1382e7fSJohn Baldwinif they are compiled in.
109a1382e7fSJohn BaldwinThis is useful for post-mortem debugging tools such as
110a1382e7fSJohn Baldwin.Xr gdb 1
111a1382e7fSJohn Baldwinthat are used to analyze kernel crash dumps.
112a1382e7fSJohn Baldwin.Pp
113a1382e7fSJohn BaldwinThe CPU event mask is stored in the
114a1382e7fSJohn Baldwin.Va ktr_cpumask
115a1382e7fSJohn Baldwinvariable.
116a1382e7fSJohn Baldwin.Pp
117a1382e7fSJohn BaldwinThe
118a1382e7fSJohn Baldwin.Va ktr_verbose
119a1382e7fSJohn Baldwinvariable stores the verbose flag that controls whether events are logged to
120a1382e7fSJohn Baldwinthe console in addition to the event buffer.
121a1382e7fSJohn Baldwin.Sh EXAMPLES
122a1382e7fSJohn BaldwinThis example demonstrates the use of tracepoints at the
123a1382e7fSJohn Baldwin.Dv KTR_PROC
124a1382e7fSJohn Baldwinlogging level.
125a1382e7fSJohn Baldwin.Bd -literal -offset indent
126a1382e7fSJohn Baldwinvoid
127a1382e7fSJohn Baldwinmi_switch()
128a1382e7fSJohn Baldwin{
129a1382e7fSJohn Baldwin	...
130a1382e7fSJohn Baldwin	/*
131a1382e7fSJohn Baldwin	 * Pick a new current process and record its start time.
132a1382e7fSJohn Baldwin	 */
133a1382e7fSJohn Baldwin	...
134a1382e7fSJohn Baldwin	CTR3(KTR_PROC, "mi_switch: old proc %p (pid %d, %s)", p, p->p_pid,
135a1382e7fSJohn Baldwin	    p->p_comm);
136a1382e7fSJohn Baldwin	...
137a1382e7fSJohn Baldwin	cpu_switch();
138a1382e7fSJohn Baldwin	...
139a1382e7fSJohn Baldwin	CTR3(KTR_PROC, "mi_switch: new proc %p (pid %d, %s)", p, p->p_pid,
140a1382e7fSJohn Baldwin	    p->p_comm);
141a1382e7fSJohn Baldwin	...
142a1382e7fSJohn Baldwin}
143a1382e7fSJohn Baldwin.Ed
144a1382e7fSJohn Baldwin.Sh SEE ALSO
145a1382e7fSJohn Baldwin.Xr ktr 4
146a1382e7fSJohn Baldwin.Sh HISTORY
147a1382e7fSJohn BaldwinThe KTR kernel tracing facility first appeared in
148a1382e7fSJohn Baldwin.Bsx 3.0
149a1382e7fSJohn Baldwinand was imported into
150a1382e7fSJohn Baldwin.Fx 5.0 .
151a1382e7fSJohn Baldwin.Sh BUGS
152a1382e7fSJohn BaldwinCurrently there is one global buffer shared among all CPUs.
153a1382e7fSJohn BaldwinIt might be profitable at some point in time to use per-CPU buffers instead
154a1382e7fSJohn Baldwinso that if one CPU halts or starts spinning, then the log messages it
155a1382e7fSJohn Baldwinemitted just prior to halting or spinning will not be drowned out by events
156a1382e7fSJohn Baldwinfrom the other CPUs.
157