25c25
< .\" $FreeBSD: stable/10/share/man/man9/SDT.9 282444 2015-05-05 03:13:02Z markj $
---
> .\" $FreeBSD: stable/10/share/man/man9/SDT.9 260817 2014-01-17 10:58:59Z avg $
27c27
< .Dd April 18, 2015
---
> .Dd August 17, 2013
34,35d33
< .In sys/param.h
< .In sys/queue.h
197,210d194
< .Sh PROVIDERS
< A number of kernel DTrace providers are available.
< In general, these providers define stable interfaces and should be treated as
< such: existing D scripts may be broken if a probe is renamed or its arguments
< are modified.
< However, it is often useful to define ad-hoc
< .Nm
< probes for debugging a subsystem or driver.
< Similarly, a developer may wish to provide a group of
< .Nm
< probes without committing to their future stability.
< Such probes should be added to the
< .Ql sdt
< provider instead of defining a new provider.
212,227d195
< The DTrace providers available on the current system can be listed with
< .Bd -literal -offset indent
< dtrace -l | sed 1d | awk '{print $2}' | sort -u
< .Ed
< .Pp
< A detailed list of the probes offered by a given provider can be obtained by
< specifying the provider using the
< .Fl P
< flag.
< For example, to view the probes and argument types for the
< .Ql sched
< provider, run
< .Bd -literal -offset indent
< dtrace -lv -P sched
< .Ed
< .Pp
229c197
< .Ql icmp:::receive-unreachable ,
---
> .Ql icmp::unreach:pkt-receive ,
235c203
< SDT_PROBE_DEFINE1(icmp, , , receive__unreachable,
---
> SDT_PROBE_DEFINE1(icmp, , unreach, pkt_receive, pkt-receive,
247c215
< SDT_PROBE_DEFINE3(ip, , , receive, "struct ifnet *",
---
> SDT_PROBE_DEFINE3(ip, , , receive, receive, "struct ifnet *",
303c271
< SDT_PROBE_DEFINE1_XLATE(ip, , , receive, "struct icmp *",
---
> SDT_PROBE_DEFINE1_XLATE(ip, , , receive, receive, "struct icmp *",
319,322c287,290
< macros allow the module and function names of a probe to be specified as part of
< a probe definition.
< The DTrace framework uses the module name of probes to determine which probes
< should be destroyed when a kernel module is unloaded, so the module
---
> macros allow the module name of a probe to be specified as part of a probe
> definition.
> However, the DTrace framework uses the module name of probes to determine
> which probes should be destroyed when a kernel module is unloaded, so the module
< .\" $FreeBSD: stable/10/share/man/man9/SDT.9 282444 2015-05-05 03:13:02Z markj $
---
> .\" $FreeBSD: stable/10/share/man/man9/SDT.9 260817 2014-01-17 10:58:59Z avg $
27c27
< .Dd April 18, 2015
---
> .Dd August 17, 2013
34,35d33
< .In sys/param.h
< .In sys/queue.h
197,210d194
< .Sh PROVIDERS
< A number of kernel DTrace providers are available.
< In general, these providers define stable interfaces and should be treated as
< such: existing D scripts may be broken if a probe is renamed or its arguments
< are modified.
< However, it is often useful to define ad-hoc
< .Nm
< probes for debugging a subsystem or driver.
< Similarly, a developer may wish to provide a group of
< .Nm
< probes without committing to their future stability.
< Such probes should be added to the
< .Ql sdt
< provider instead of defining a new provider.
212,227d195
< The DTrace providers available on the current system can be listed with
< .Bd -literal -offset indent
< dtrace -l | sed 1d | awk '{print $2}' | sort -u
< .Ed
< .Pp
< A detailed list of the probes offered by a given provider can be obtained by
< specifying the provider using the
< .Fl P
< flag.
< For example, to view the probes and argument types for the
< .Ql sched
< provider, run
< .Bd -literal -offset indent
< dtrace -lv -P sched
< .Ed
< .Pp
229c197
< .Ql icmp:::receive-unreachable ,
---
> .Ql icmp::unreach:pkt-receive ,
235c203
< SDT_PROBE_DEFINE1(icmp, , , receive__unreachable,
---
> SDT_PROBE_DEFINE1(icmp, , unreach, pkt_receive, pkt-receive,
247c215
< SDT_PROBE_DEFINE3(ip, , , receive, "struct ifnet *",
---
> SDT_PROBE_DEFINE3(ip, , , receive, receive, "struct ifnet *",
303c271
< SDT_PROBE_DEFINE1_XLATE(ip, , , receive, "struct icmp *",
---
> SDT_PROBE_DEFINE1_XLATE(ip, , , receive, receive, "struct icmp *",
319,322c287,290
< macros allow the module and function names of a probe to be specified as part of
< a probe definition.
< The DTrace framework uses the module name of probes to determine which probes
< should be destroyed when a kernel module is unloaded, so the module
---
> macros allow the module name of a probe to be specified as part of a probe
> definition.
> However, the DTrace framework uses the module name of probes to determine
> which probes should be destroyed when a kernel module is unloaded, so the module