Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Jul 2012 09:53:21 +0000 (UTC)
From:      Martin Matuska <mm@FreeBSD.org>
To:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-vendor@freebsd.org
Subject:   svn commit: r238581 - vendor/illumos/dist/man/man1m
Message-ID:  <201207180953.q6I9rLQF052608@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: mm
Date: Wed Jul 18 09:53:20 2012
New Revision: 238581
URL: http://svn.freebsd.org/changeset/base/238581

Log:
  Import relevant vendor manual pages from illumos-gate
  revision 13304:b54231762cfa
  
  Obtained from:	ssh://anonhg@hg.illumos.org/illumos-gate

Added:
  vendor/illumos/dist/man/man1m/lockstat.1m
  vendor/illumos/dist/man/man1m/plockstat.1m
  vendor/illumos/dist/man/man1m/zdb.1m
  vendor/illumos/dist/man/man1m/zfs.1m
  vendor/illumos/dist/man/man1m/zpool.1m
  vendor/illumos/dist/man/man1m/zstreamdump.1m
Modified:
  vendor/illumos/dist/man/man1m/dtrace.1m

Modified: vendor/illumos/dist/man/man1m/dtrace.1m
==============================================================================
--- vendor/illumos/dist/man/man1m/dtrace.1m	Wed Jul 18 09:47:48 2012	(r238580)
+++ vendor/illumos/dist/man/man1m/dtrace.1m	Wed Jul 18 09:53:20 2012	(r238581)
@@ -1,51 +1,42 @@
 '\" te
-.\" CDDL HEADER START
-.\"
-.\" The contents of this file are subject to the terms of the
-.\" Common Development and Distribution License (the "License").  
-.\" You may not use this file except in compliance with the License.
-.\"
-.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
-.\" or http://www.opensolaris.org/os/licensing.
-.\" See the License for the specific language governing permissions
-.\" and limitations under the License.
-.\"
-.\" When distributing Covered Code, include this CDDL HEADER in each
-.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
-.\" If applicable, add the following below this CDDL HEADER, with the
-.\" fields enclosed by brackets "[]" replaced with your own identifying
-.\" information: Portions Copyright [yyyy] [name of copyright owner]
-.\"
-.\" CDDL HEADER END
-.\" Copyright (c) 2006, Sun Microsystems, Inc. All Rights Reserved.
-.TH dtrace 1M "5 Sep 2006" "SunOS 5.11" "System Administration Commands"
+.\" Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved.
+.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
+.\" See the License for the specific language governing permissions and limitations under the License. When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the
+.\" fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
+.TH dtrace 1M "4 Aug 2009" "SunOS 5.11" "System Administration Commands"
 .SH NAME
 dtrace \- DTrace dynamic tracing compiler and tracing utility
 .SH SYNOPSIS
 .LP
 .nf
 \fBdtrace\fR [\fB-32\fR | \fB-64\fR] [\fB-aACeFGHhlqSvVwZ\fR] [\fB-b\fR \fIbufsz\fR] [\fB-c\fR \fIcmd\fR] 
-    [\fB-D\fR \fIname\fR [\fI=value\fR]] [\fB-I\fR \fIpath\fR] [\fB-L\fR \fIpath\fR] [\fB-o\fR \fIoutput\fR] 
-    [\fB-s\fR \fIscript\fR] [\fB-U\fR \fIname\fR] [\fB-x\fR \fIarg\fR [\fI=val\fR]] 
-    [\fB-X\fR a | c | s | t] [\fB-p\fR \fIpid\fR] 
-    [\fB-P\fR \fIprovider\fR [[\fIpredicate\fR] \fIaction\fR]] 
-    [\fB-m\fR [\fIprovider:\fR] \fImodule\fR [[\fIpredicate\fR] \fIaction\fR]] 
-    [\fB-f\fR [[\fIprovider:\fR] \fImodule:\fR] \fIfunction\fR [[\fIpredicate\fR] \fIaction\fR]] 
-    [\fB-n\fR [[[\fIprovider:\fR] \fImodule:\fR] \fIfunction:\fR] \fIname\fR [[\fIpredicate\fR] \fIaction\fR]] 
-    [\fB-i\fR \fIprobe-id\fR [[\fIpredicate\fR] \fIaction\fR]]
+     [\fB-D\fR \fIname\fR [\fI=value\fR]] [\fB-I\fR \fIpath\fR] [\fB-L\fR \fIpath\fR] [\fB-o\fR \fIoutput\fR] 
+     [\fB-s\fR \fIscript\fR] [\fB-U\fR \fIname\fR] [\fB-x\fR \fIarg\fR [\fI=val\fR]] 
+     [\fB-X\fR a | c | s | t] [\fB-p\fR \fIpid\fR] 
+     [\fB-P\fR \fIprovider\fR [[\fIpredicate\fR] \fIaction\fR]] 
+     [\fB-m\fR [\fIprovider:\fR] \fImodule\fR [[\fIpredicate\fR] \fIaction\fR]] 
+     [\fB-f\fR [[\fIprovider:\fR] \fImodule:\fR] \fIfunction\fR [[\fIpredicate\fR] \fIaction\fR]] 
+     [\fB-n\fR [[[\fIprovider:\fR] \fImodule:\fR] \fIfunction:\fR] \fIname\fR [[\fIpredicate\fR] \fIaction\fR]] 
+     [\fB-i\fR \fIprobe-id\fR [[\fIpredicate\fR] \fIaction\fR]]
 .fi
 
 .SH DESCRIPTION
 .sp
 .LP
-DTrace is a comprehensive dynamic tracing framework for the Solaris Operating System. DTrace provides a powerful infrastructure that permits administrators, developers, and service personnel to concisely answer arbitrary questions about the behavior of the operating system and user programs. 
+DTrace is a comprehensive dynamic tracing framework for the Solaris Operating
+System. DTrace provides a powerful infrastructure that permits administrators,
+developers, and service personnel to concisely answer arbitrary questions about
+the behavior of the operating system and user programs.
 .sp
 .LP
-The \fISolaris Dynamic Tracing Guide\fR describes how to use DTrace to observe, debug, and tune system behavior. Refer to this book for a detailed description of DTrace features, including the bundled DTrace observability
-tools, instrumentation providers, and the D programming language.
+The \fISolaris Dynamic Tracing Guide\fR describes how to use DTrace to observe,
+debug, and tune system behavior. Refer to this book for a detailed description
+of DTrace features, including the bundled DTrace observability tools,
+instrumentation providers, and the D programming language.
 .sp
 .LP
-The \fBdtrace\fR command provides a generic interface to the essential services provided by the DTrace facility, including:
+The \fBdtrace\fR command provides a generic interface to the essential services
+provided by the DTrace facility, including:
 .RS +4
 .TP
 .ie t \(bu
@@ -56,13 +47,15 @@ Options that list the set of probes and 
 .TP
 .ie t \(bu
 .el o
-Options that enable probes directly using any of the probe description specifiers (provider, module, function, name)
+Options that enable probes directly using any of the probe description
+specifiers (provider, module, function, name)
 .RE
 .RS +4
 .TP
 .ie t \(bu
 .el o
-Options that run the D compiler and compile one or more D program files or programs written directly on the command line
+Options that run the D compiler and compile one or more D program files or
+programs written directly on the command line
 .RE
 .RS +4
 .TP
@@ -80,15 +73,25 @@ Options that generate program stability 
 .TP
 .ie t \(bu
 .el o
-Options that modify DTrace tracing and buffering behavior and enable additional D compiler features
+Options that modify DTrace tracing and buffering behavior and enable additional
+D compiler features
 .RE
 .sp
 .LP
-You can use \fBdtrace\fR to create D scripts by using it in a \fB#!\fR declaration to create an interpreter file. You can also use \fBdtrace\fR to attempt to compile D programs and determine their properties without actually enabling tracing using the \fB-e\fR option. See \fBOPTIONS\fR. See the \fISolaris Dynamic Tracing Guide\fR for detailed examples of how to use the \fBdtrace\fR utility to perform these tasks.
+You can use \fBdtrace\fR to create D scripts by using it in a \fB#!\fR
+declaration to create an interpreter file. You can also use \fBdtrace\fR to
+attempt to compile D programs and determine their properties without actually
+enabling tracing using the \fB-e\fR option. See \fBOPTIONS\fR. See the
+\fISolaris Dynamic Tracing Guide\fR for detailed examples of how to use the
+\fBdtrace\fR utility to perform these tasks.
 .SH OPTIONS
 .sp
 .LP
-The arguments accepted by the \fB-P\fR, \fB-m\fR, \fB-f\fR, \fB-n\fR, and \fB-i\fR options can include an optional D language \fIpredicate\fR enclosed in slashes \fB//\fR and optional D language \fIaction\fR statement list enclosed in braces \fB{}\fR. D program code specified on the command line must be appropriately quoted to avoid intepretation of meta-characters by the shell. 
+The arguments accepted by the \fB-P\fR, \fB-m\fR, \fB-f\fR, \fB-n\fR, and
+\fB-i\fR options can include an optional D language \fIpredicate\fR enclosed in
+slashes \fB//\fR and optional D language \fIaction\fR statement list enclosed
+in braces \fB{}\fR. D program code specified on the command line must be
+appropriately quoted to avoid interpretation of meta-characters by the shell.
 .sp
 .LP
 The following options are supported:
@@ -100,10 +103,17 @@ The following options are supported:
 .ad
 .sp .6
 .RS 4n
-The D compiler produces programs using the native data model of the operating system kernel. You can use the \fBisainfo\fR \fB-b\fR command to determine the current operating system data model.  If the \fB-32\fR option is specified, \fBdtrace\fR forces
-the D compiler to compile a D program using the 32-bit data model. If the \fB-64\fR option is specified, \fBdtrace\fR forces the D compiler to compile a D program using the 64-bit data model. These options are typically not required as \fBdtrace\fR selects the
-native data model as the default. The data model affects the sizes of integer types and other language properties. D programs compiled for either data model can be executed on both 32-bit and 64-bit kernels. The \fB-32\fR and \fB-64\fR options also determine the ELF file format
-(ELF32 or ELF64) produced by the \fB-G\fR option.
+The D compiler produces programs using the native data model of the operating
+system kernel. You can use the \fBisainfo\fR \fB-b\fR command to determine the
+current operating system data model. If the \fB-32\fR option is specified,
+\fBdtrace\fR forces the D compiler to compile a D program using the 32-bit data
+model. If the \fB-64\fR option is specified, \fBdtrace\fR forces the D compiler
+to compile a D program using the 64-bit data model. These options are typically
+not required as \fBdtrace\fR selects the native data model as the default. The
+data model affects the sizes of integer types and other language properties. D
+programs compiled for either data model can be executed on both 32-bit and
+64-bit kernels. The \fB-32\fR and \fB-64\fR options also determine the ELF file
+format (ELF32 or ELF64) produced by the \fB-G\fR option.
 .RE
 
 .sp
@@ -114,8 +124,11 @@ native data model as the default. The da
 .ad
 .sp .6
 .RS 4n
-Claim anonymous tracing state and display the traced data. You can combine the \fB-a\fR option with the \fB-e\fR option to force \fBdtrace\fR to exit immediately after consuming the anonymous tracing state rather than continuing to wait for new
-data. See the \fISolaris Dynamic Tracing Guide\fR for more information about anonymous tracing.
+Claim anonymous tracing state and display the traced data. You can combine the
+\fB-a\fR option with the \fB-e\fR option to force \fBdtrace\fR to exit
+immediately after consuming the anonymous tracing state rather than continuing
+to wait for new data. See the \fISolaris Dynamic Tracing Guide\fR for more
+information about anonymous tracing.
 .RE
 
 .sp
@@ -126,7 +139,12 @@ data. See the \fISolaris Dynamic Tracing
 .ad
 .sp .6
 .RS 4n
-Generate \fBdriver.conf\fR(4) directives for anonymous tracing. This option constructs a set of \fBdtrace\fR(7D) configuration file directives to enable the specified probes for anonymous tracing and then exits. By default, \fBdtrace\fR attempts to store the directives to the file \fB/kernel/drv/dtrace.conf\fR. You can modify this behavior if you use the \fB-o\fR option to specify an alternate output file.
+Generate \fBdriver.conf\fR(4) directives for anonymous tracing. This option
+constructs a set of \fBdtrace\fR(7D) configuration file directives to enable
+the specified probes for anonymous tracing and then exits. By default,
+\fBdtrace\fR attempts to store the directives to the file
+\fB/kernel/drv/dtrace.conf\fR. You can modify this behavior if you use the
+\fB-o\fR option to specify an alternate output file.
 .RE
 
 .sp
@@ -137,8 +155,10 @@ Generate \fBdriver.conf\fR(4) directives
 .ad
 .sp .6
 .RS 4n
-Set principal trace buffer size (\fIbufsz\fR). The trace buffer size can include any of the size suffixes \fBk\fR, \fBm\fR, \fBg\fR, or \fBt\fR.  If the buffer space cannot be allocated, \fBdtrace\fR attempts
-to reduce the buffer size or exit depending on the setting of the \fBbufresize\fR property.
+Set principal trace buffer size (\fIbufsz\fR). The trace buffer size can
+include any of the size suffixes \fBk\fR, \fBm\fR, \fBg\fR, or \fBt\fR. If the
+buffer space cannot be allocated, \fBdtrace\fR attempts to reduce the buffer
+size or exit depending on the setting of the \fBbufresize\fR property.
 .RE
 
 .sp
@@ -149,9 +169,13 @@ to reduce the buffer size or exit depend
 .ad
 .sp .6
 .RS 4n
-Run the specified command \fIcmd\fR and exit upon its completion. If more than one \fB-c\fR option is present on the command line, \fBdtrace\fR exits when all commands have exited, reporting the exit status for each child process as it
-terminates. The process-ID of the first command is made available to any D programs specified on the command line or using the \fB-s\fR option through the \fB$target\fR macro variable. Refer to the \fISolaris Dynamic Tracing Guide\fR for more information
-on macro variables.
+Run the specified command \fIcmd\fR and exit upon its completion. If more than
+one \fB-c\fR option is present on the command line, \fBdtrace\fR exits when all
+commands have exited, reporting the exit status for each child process as it
+terminates. The process-ID of the first command is made available to any D
+programs specified on the command line or using the \fB-s\fR option through the
+\fB$target\fR macro variable. Refer to the \fISolaris Dynamic Tracing Guide\fR
+for more information on macro variables.
 .RE
 
 .sp
@@ -162,7 +186,11 @@ on macro variables.
 .ad
 .sp .6
 .RS 4n
-Run the C preprocessor \fBcpp\fR(1) over D programs before compiling them. You can pass options to the C preprocessor using the \fB-D\fR, \fB-U\fR, \fB-I\fR, and \fB-H\fR options. You can select the degree of C standard conformance if you use the \fB-X\fR option. For a description of the set of tokens defined by the D compiler when invoking the C preprocessor, see \fB-X\fR.
+Run the C preprocessor \fBcpp\fR(1) over D programs before compiling them. You
+can pass options to the C preprocessor using the \fB-D\fR, \fB-U\fR, \fB-I\fR,
+and \fB-H\fR options. You can select the degree of C standard conformance if
+you use the \fB-X\fR option. For a description of the set of tokens defined by
+the D compiler when invoking the C preprocessor, see \fB-X\fR.
 .RE
 
 .sp
@@ -173,8 +201,10 @@ Run the C preprocessor \fBcpp\fR(1) over
 .ad
 .sp .6
 .RS 4n
-Define \fIname\fR when invoking \fBcpp\fR(1) (enabled using the \fB-C\fR option). If you specify the equals sign (\fB=\fR)
-and additional \fIvalue\fR, the name is assigned the corresponding value. This option passes the \fB-D\fR option to each \fBcpp\fR invocation.
+Define \fIname\fR when invoking \fBcpp\fR(1) (enabled using the \fB-C\fR
+option). If you specify the equals sign (\fB=\fR) and additional \fIvalue\fR,
+the name is assigned the corresponding value. This option passes the \fB-D\fR
+option to each \fBcpp\fR invocation.
 .RE
 
 .sp
@@ -185,21 +215,32 @@ and additional \fIvalue\fR, the name is 
 .ad
 .sp .6
 .RS 4n
-Exit after compiling any requests and consuming anonymous tracing state (\fB-a\fR option) but prior to enabling any probes. You can combine this option with the \fB-a\fR option to print anonymous tracing data and exit. You can also combine this option with D
-compiler options. This combination verifies that the programs compile without actually executing them and enabling the corresponding instrumentation.
+Exit after compiling any requests and consuming anonymous tracing state
+(\fB-a\fR option) but prior to enabling any probes. You can combine this option
+with the \fB-a\fR option to print anonymous tracing data and exit. You can also
+combine this option with D compiler options. This combination verifies that the
+programs compile without actually executing them and enabling the corresponding
+instrumentation.
 .RE
 
 .sp
 .ne 2
 .mk
 .na
-\fB\fB-f\fR\fB[[\fR\fIprovider\fR\fB:]\fR\fImodule\fR\fB:]\fR\fIfunction\fR\fB[[\fR\fIpredicate\fR\fB]\fR\fIaction\fR\fB]]\fR\fR
+\fB\fB-f\fR\fB[[\fR\fIprovider\fR\fB:]\fR\fImodule\fR\fB:]\fR\fIfunction\fR\fB[
+[\fR\fIpredicate\fR\fB]\fR\fIaction\fR\fB]]\fR\fR
 .ad
 .sp .6
 .RS 4n
-Specify function name to trace or list (\fB-l\fR option). The corresponding argument can include any of the probe description forms \fIprovider:module:function\fR, \fImodule:function\fR, or \fIfunction\fR.
-Unspecified probe description fields are left blank and match any probes regardless of the values in those fields. If no qualifiers other than \fIfunction\fR are specified in the description, all probes with the corresponding \fIfunction\fR are matched.
-The \fB-f\fR argument can be suffixed with an optional D probe clause. You can specify more than one \fB-f\fR option on the command line at a time.
+Specify function name to trace or list (\fB-l\fR option). The corresponding
+argument can include any of the probe description forms
+\fIprovider:module:function\fR, \fImodule:function\fR, or \fIfunction\fR.
+Unspecified probe description fields are left blank and match any probes
+regardless of the values in those fields. If no qualifiers other than
+\fIfunction\fR are specified in the description, all probes with the
+corresponding \fIfunction\fR are matched. The \fB-f\fR argument can be suffixed
+with an optional D probe clause. You can specify more than one \fB-f\fR option
+on the command line at a time.
 .RE
 
 .sp
@@ -210,8 +251,12 @@ The \fB-f\fR argument can be suffixed wi
 .ad
 .sp .6
 .RS 4n
-Coalesce trace output by identifying function entry and return. Function entry probe reports are indented and their output is prefixed with \fB->\fR. Function return probe reports are unindented and their output is prefixed with \fB<-\fR\&. System call
-entry probe reports are indented and their output is prefixed with \fB=>\fR. System call return probe reports are unindented and their output is prefixed with \fB<=\fR\&.
+Coalesce trace output by identifying function entry and return. Function entry
+probe reports are indented and their output is prefixed with \fB->\fR. Function
+return probe reports are unindented and their output is prefixed with
+\fB<-\fR\&. System call entry probe reports are indented and their output is
+prefixed with \fB=>\fR. System call return probe reports are unindented and
+their output is prefixed with \fB<=\fR\&.
 .RE
 
 .sp
@@ -222,9 +267,14 @@ entry probe reports are indented and the
 .ad
 .sp .6
 .RS 4n
-Generate an ELF file containing an embedded DTrace program. The DTrace probes specified in the program are saved inside of a relocatable ELF object which can be linked into another program. If the \fB-o\fR option is present, the ELF file is saved using the pathname specified
-as the argument for this operand. If the \fB-o\fR option is not present and the DTrace program is contained with a file whose name is \fB\fIfilename\fR.d\fR, then the ELF file is saved using the name \fB\fIfilename\fR.o\fR.
-Otherwise the ELF file is saved using the name \fBd.out\fR.
+Generate an ELF file containing an embedded DTrace program. The DTrace probes
+specified in the program are saved inside of a relocatable ELF object which can
+be linked into another program. If the \fB-o\fR option is present, the ELF file
+is saved using the pathname specified as the argument for this operand. If the
+\fB-o\fR option is not present and the DTrace program is contained with a file
+whose name is \fB\fIfilename\fR.d\fR, then the ELF file is saved using the name
+\fB\fIfilename\fR.o\fR. Otherwise the ELF file is saved using the name
+\fBd.out\fR.
 .RE
 
 .sp
@@ -235,8 +285,10 @@ Otherwise the ELF file is saved using th
 .ad
 .sp .6
 .RS 4n
-Print the pathnames of included files when invoking \fBcpp\fR(1) (enabled using the \fB-C\fR option). This option passes the \fB-H\fR option
-to each \fBcpp\fR invocation, causing it to display the list of pathnames, one for each line, to \fBstderr\fR.
+Print the pathnames of included files when invoking \fBcpp\fR(1) (enabled using
+the \fB-C\fR option). This option passes the \fB-H\fR option to each \fBcpp\fR
+invocation, causing it to display the list of pathnames, one for each line, to
+\fBstderr\fR.
 .RE
 
 .sp
@@ -247,9 +299,14 @@ to each \fBcpp\fR invocation, causing it
 .ad
 .sp .6
 .RS 4n
-Generate a header file containing macros that correspond to probes in the specified provider definitions. This option should be used to generate a header file that is included by other source files for later use with the \fB-G\fR option. If the \fB-o\fR option
-is present, the header file is saved using the pathname specified as the argument for that option. If the \fB-o\fR option is not present and the DTrace program is contained with a file whose name is \fIfilename\fR\fB\&.d\fR, then the header file is saved
-using the name \fIfilename\fR\fB\&.h\fR.
+Generate a header file containing macros that correspond to probes in the
+specified provider definitions. This option should be used to generate a header
+file that is included by other source files for later use with the \fB-G\fR
+option. If the \fB-o\fR option is present, the header file is saved using the
+pathname specified as the argument for that option. If the \fB-o\fR option is
+not present and the DTrace program is contained with a file whose name is
+\fIfilename\fR\fB\&.d\fR, then the header file is saved using the name
+\fIfilename\fR\fB\&.h\fR.
 .RE
 
 .sp
@@ -260,8 +317,10 @@ using the name \fIfilename\fR\fB\&.h\fR.
 .ad
 .sp .6
 .RS 4n
-Specify probe identifier (\fIprobe-id\fR) to trace or list (\fB-l\fR option). You can specify probe IDs using decimal integers as shown by \fBdtrace\fR \fB-l\fR. The \fB-i\fR argument can be suffixed with an optional
-D probe clause. You can specify more than one \fB-i\fR option at a time.
+Specify probe identifier (\fIprobe-id\fR) to trace or list (\fB-l\fR option).
+You can specify probe IDs using decimal integers as shown by \fBdtrace\fR
+\fB-l\fR. The \fB-i\fR argument can be suffixed with an optional D probe
+clause. You can specify more than one \fB-i\fR option at a time.
 .RE
 
 .sp
@@ -272,8 +331,11 @@ D probe clause. You can specify more tha
 .ad
 .sp .6
 .RS 4n
-Add the specified directory \fIpath\fR to the search path for \fB#include\fR files when invoking \fBcpp\fR(1) (enabled
-using the \fB-C\fR option). This option passes the \fB-I\fR option to each \fBcpp\fR invocation. The specified \fIpath\fR is inserted into the search path ahead of the default directory list.
+Add the specified directory \fIpath\fR to the search path for \fB#include\fR
+files when invoking \fBcpp\fR(1) (enabled using the \fB-C\fR option). This
+option passes the \fB-I\fR option to each \fBcpp\fR invocation. The specified
+\fIpath\fR is inserted into the search path ahead of the default directory
+list.
 .RE
 
 .sp
@@ -284,7 +346,9 @@ using the \fB-C\fR option). This option 
 .ad
 .sp .6
 .RS 4n
-Add the specified directory \fIpath\fR to the search path for DTrace libraries. DTrace libraries are used to contain common definitions that can be used when writing D programs. The specified \fIpath\fR is added after the default library
+Add the specified directory \fIpath\fR to the search path for DTrace libraries.
+DTrace libraries are used to contain common definitions that can be used when
+writing D programs. The specified \fIpath\fR is added after the default library
 search path.
 .RE
 
@@ -296,34 +360,49 @@ search path.
 .ad
 .sp .6
 .RS 4n
-List probes instead of enabling them. If the \fB-l\fR option is specified, \fBdtrace\fR produces a report of the probes matching the descriptions given using the \fB-P\fR, \fB-m\fR, \fB-f\fR, \fB-n\fR, \fB-i\fR,
-and \fB-s\fR options. If none of these options are specified, this option lists all probes.
+List probes instead of enabling them. If the \fB-l\fR option is specified,
+\fBdtrace\fR produces a report of the probes matching the descriptions given
+using the \fB-P\fR, \fB-m\fR, \fB-f\fR, \fB-n\fR, \fB-i\fR, and \fB-s\fR
+options. If none of these options are specified, this option lists all probes.
 .RE
 
 .sp
 .ne 2
 .mk
 .na
-\fB\fB-m\fR [[\fIprovider:\fR] \fImodule:\fR [[\fIpredicate\fR] \fIaction\fR]]\fR
+\fB\fB-m\fR [[\fIprovider:\fR] \fImodule:\fR [[\fIpredicate\fR]
+\fIaction\fR]]\fR
 .ad
 .sp .6
 .RS 4n
-Specify module name to trace or list (\fB-l\fR option). The corresponding argument can include any of the probe description forms \fIprovider:module\fR or \fImodule\fR. Unspecified probe description fields are left blank and match
-any probes regardless of the values in those fields. If no qualifiers other than \fImodule\fR are specified in the description, all probes with a corresponding \fImodule\fR are matched. The \fB-m\fR argument can be suffixed with an optional D
-probe clause. More than one \fB-m\fR option can be specified on the command line at a time.
+Specify module name to trace or list (\fB-l\fR option). The corresponding
+argument can include any of the probe description forms \fIprovider:module\fR
+or \fImodule\fR. Unspecified probe description fields are left blank and match
+any probes regardless of the values in those fields. If no qualifiers other
+than \fImodule\fR are specified in the description, all probes with a
+corresponding \fImodule\fR are matched. The \fB-m\fR argument can be suffixed
+with an optional D probe clause. More than one \fB-m\fR option can be specified
+on the command line at a time.
 .RE
 
 .sp
 .ne 2
 .mk
 .na
-\fB\fB-n\fR [[[\fIprovider:\fR] \fImodule:\fR] \fIfunction:\fR] \fIname\fR [[\fIpredicate\fR] \fIaction\fR]\fR
+\fB\fB-n\fR [[[\fIprovider:\fR] \fImodule:\fR] \fIfunction:\fR] \fIname\fR
+[[\fIpredicate\fR] \fIaction\fR]\fR
 .ad
 .sp .6
 .RS 4n
-Specify probe name to trace or list (\fB-l\fR option). The corresponding argument can include any of the probe description forms \fIprovider:module:function:name\fR, \fImodule:function:name\fR, \fIfunction:name\fR,
-or \fIname\fR.  Unspecified probe description fields are left blank and match any probes regardless of the values in those fields. If no qualifiers other than \fIname\fR are specified in the description, all probes with a corresponding \fIname\fR are
-matched. The \fB-n\fR argument can be suffixed with an optional D probe clause. More than one \fB-n\fR option can be specified on the command line at a time.
+Specify probe name to trace or list (\fB-l\fR option). The corresponding
+argument can include any of the probe description forms
+\fIprovider:module:function:name\fR, \fImodule:function:name\fR,
+\fIfunction:name\fR, or \fIname\fR. Unspecified probe description fields are
+left blank and match any probes regardless of the values in those fields. If no
+qualifiers other than \fIname\fR are specified in the description, all probes
+with a corresponding \fIname\fR are matched. The \fB-n\fR argument can be
+suffixed with an optional D probe clause. More than one \fB-n\fR option can be
+specified on the command line at a time.
 .RE
 
 .sp
@@ -334,8 +413,13 @@ matched. The \fB-n\fR argument can be su
 .ad
 .sp .6
 .RS 4n
-Specify the \fIoutput\fR file for the \fB-A\fR , \fB-G\fR, and \fB-l\fR options, or for the traced data itself. If the \fB-A\fR option is present and \fB-o\fR is not present, the default output file is \fB/kernel/drv/dtrace.conf\fR. If the \fB-G\fR option is present and the \fB-s\fR option's argument is of the form \fB\fIfilename\fR.d\fR and \fB-o\fR is not present, the default output file is \fB\fIfilename\fR.o\fR.
-Otherwise the default output file is \fBd.out\fR.
+Specify the \fIoutput\fR file for the \fB-A\fR , \fB-G\fR,  \fB-h\fR, and
+\fB-l\fR options, or for the traced data itself. If the \fB-A\fR option is
+present and \fB-o\fR is not present, the default output file is
+\fB/kernel/drv/dtrace.conf\fR. If the \fB-G\fR option is present and the
+\fB-s\fR option's argument is of the form \fB\fIfilename\fR.d\fR and \fB-o\fR
+is not present, the default output file is \fB\fIfilename\fR.o\fR. Otherwise
+the default output file is \fBd.out\fR.
 .RE
 
 .sp
@@ -346,9 +430,13 @@ Otherwise the default output file is \fB
 .ad
 .sp .6
 .RS 4n
-Grab the specified process-ID \fIpid\fR, cache its symbol tables, and exit upon its completion. If more than one \fB-p\fR option is present on the command line, \fBdtrace\fR exits when all commands have exited, reporting the exit status
-for each process as it terminates. The first process-ID is made available to any D programs specified on the command line or using the \fB-s\fR option through the \fB$target\fR macro variable. Refer to the \fISolaris Dynamic Tracing Guide\fR for
-more information on macro variables.
+Grab the specified process-ID \fIpid\fR, cache its symbol tables, and exit upon
+its completion. If more than one \fB-p\fR option is present on the command
+line, \fBdtrace\fR exits when all commands have exited, reporting the exit
+status for each process as it terminates. The first process-ID is made
+available to any D programs specified on the command line or using the \fB-s\fR
+option through the \fB$target\fR macro variable. Refer to the \fISolaris
+Dynamic Tracing Guide\fR for more information on macro variables.
 .RE
 
 .sp
@@ -359,8 +447,11 @@ more information on macro variables.
 .ad
 .sp .6
 .RS 4n
-Specify provider name to trace or list (\fB-l\fR option). The remaining probe description fields module, function, and name are left blank and match any probes regardless of the values in those fields. The \fB-P\fR argument can be suffixed with an optional D
-probe clause. You can specify more than one \fB-P\fR option on the command line at a time.
+Specify provider name to trace or list (\fB-l\fR option). The remaining probe
+description fields module, function, and name are left blank and match any
+probes regardless of the values in those fields. The \fB-P\fR argument can be
+suffixed with an optional D probe clause. You can specify more than one
+\fB-P\fR option on the command line at a time.
 .RE
 
 .sp
@@ -371,8 +462,11 @@ probe clause. You can specify more than 
 .ad
 .sp .6
 .RS 4n
-Set quiet mode. \fBdtrace\fR suppresses messages such as the number of probes matched by the specified options and D programs and does not print column headers, the CPU ID, the probe ID, or insert newlines into the output. Only data traced and formatted by D program
-statements such as \fBtrace()\fR and \fBprintf()\fR is displayed to \fBstdout\fR.
+Set quiet mode. \fBdtrace\fR suppresses messages such as the number of probes
+matched by the specified options and D programs and does not print column
+headers, the CPU ID, the probe ID, or insert newlines into the output. Only
+data traced and formatted by D program statements such as \fBtrace()\fR and
+\fBprintf()\fR is displayed to \fBstdout\fR.
 .RE
 
 .sp
@@ -383,8 +477,12 @@ statements such as \fBtrace()\fR and \fB
 .ad
 .sp .6
 .RS 4n
-Compile the specified D program source file. If the \fB-e\fR option is present, the program is compiled but instrumentation is not enabled. If the \fB-l\fR option is present, the program is compiled and the set of probes matched by it is listed, but instrumentation
-is not enabled. If none of \fB-e\fR, \fB-l\fR, \fB-G\fR, or \fB-A\fR are present, the instrumentation specified by the D program is enabled and tracing begins.
+Compile the specified D program source file. If the \fB-e\fR option is present,
+the program is compiled but instrumentation is not enabled. If the \fB-l\fR
+option is present, the program is compiled and the set of probes matched by it
+is listed, but instrumentation is not enabled. If none of \fB-e\fR, \fB-l\fR,
+\fB-G\fR, or \fB-A\fR are present, the instrumentation specified by the D
+program is enabled and tracing begins.
 .RE
 
 .sp
@@ -395,7 +493,8 @@ is not enabled. If none of \fB-e\fR, \fB
 .ad
 .sp .6
 .RS 4n
-Show D compiler intermediate code. The D compiler produces a report of the intermediate code generated for each D program to \fBstderr\fR.
+Show D compiler intermediate code. The D compiler produces a report of the
+intermediate code generated for each D program to \fBstderr\fR.
 .RE
 
 .sp
@@ -406,7 +505,9 @@ Show D compiler intermediate code. The D
 .ad
 .sp .6
 .RS 4n
-Undefine the specified \fIname\fR when invoking \fBcpp\fR(1) (enabled using the \fB-C\fR option). This option passes the \fB-U\fR option to each \fBcpp\fR invocation.
+Undefine the specified \fIname\fR when invoking \fBcpp\fR(1) (enabled using the
+\fB-C\fR option). This option passes the \fB-U\fR option to each \fBcpp\fR
+invocation.
 .RE
 
 .sp
@@ -417,7 +518,10 @@ Undefine the specified \fIname\fR when i
 .ad
 .sp .6
 .RS 4n
-Set verbose mode. If the \fB-v\fR option is specified, \fBdtrace\fR produces a program stability report showing the minimum interface stability and dependency level for the specified D programs. DTrace stability levels are explained in further detail in the \fISolaris Dynamic Tracing Guide\fR.
+Set verbose mode. If the \fB-v\fR option is specified, \fBdtrace\fR produces a
+program stability report showing the minimum interface stability and dependency
+level for the specified D programs. DTrace stability levels are explained in
+further detail in the \fISolaris Dynamic Tracing Guide\fR.
 .RE
 
 .sp
@@ -428,8 +532,10 @@ Set verbose mode. If the \fB-v\fR option
 .ad
 .sp .6
 .RS 4n
-Report the highest D programming interface version supported by \fBdtrace\fR. The version information is printed to \fBstdout\fR and the \fBdtrace\fR command exits. Refer to the \fISolaris Dynamic Tracing Guide\fR for
-more information about DTrace versioning features.
+Report the highest D programming interface version supported by \fBdtrace\fR.
+The version information is printed to \fBstdout\fR and the \fBdtrace\fR command
+exits. Refer to the \fISolaris Dynamic Tracing Guide\fR for more information
+about DTrace versioning features.
 .RE
 
 .sp
@@ -440,8 +546,10 @@ more information about DTrace versioning
 .ad
 .sp .6
 .RS 4n
-Permit destructive actions in D programs specified using the \fB-s\fR, \fB-P\fR, \fB-m\fR, \fB-f\fR, \fB-n\fR, or \fB-i\fR options. If the \fB-w\fR option is not specified, \fBdtrace\fR does not
-permit the compilation or enabling of a D program that contains destructive actions.
+Permit destructive actions in D programs specified using the \fB-s\fR,
+\fB-P\fR, \fB-m\fR, \fB-f\fR, \fB-n\fR, or \fB-i\fR options. If the \fB-w\fR
+option is not specified, \fBdtrace\fR does not permit the compilation or
+enabling of a D program that contains destructive actions.
 .RE
 
 .sp
@@ -452,8 +560,10 @@ permit the compilation or enabling of a 
 .ad
 .sp .6
 .RS 4n
-Enable or modify a DTrace runtime option or D compiler option. The list of options is found in the \fISolaris Dynamic Tracing Guide\fR.  Boolean options are enabled by specifying their name. Options with values are set by separating the option name and
-value with an equals sign (\fB=\fR).
+Enable or modify a DTrace runtime option or D compiler option. The list of
+options is found in the \fISolaris Dynamic Tracing Guide\fR. Boolean options
+are enabled by specifying their name. Options with values are set by separating
+the option name and value with an equals sign (\fB=\fR).
 .RE
 
 .sp
@@ -464,8 +574,10 @@ value with an equals sign (\fB=\fR).
 .ad
 .sp .6
 .RS 4n
-Specify the degree of conformance to the ISO C standard that should be selected when invoking \fBcpp\fR(1) (enabled using the \fB-C\fR option).
-The \fB-X\fR option argument affects the value and presence of the \fB__STDC__\fR macro depending upon the value of the argument letter.
+Specify the degree of conformance to the ISO C standard that should be selected
+when invoking \fBcpp\fR(1) (enabled using the \fB-C\fR option). The \fB-X\fR
+option argument affects the value and presence of the \fB__STDC__\fR macro
+depending upon the value of the argument letter.
 .sp
 The \fB-X\fR option supports the following arguments:
 .sp
@@ -476,8 +588,10 @@ The \fB-X\fR option supports the followi
 .ad
 .RS 5n
 .rt  
-Default. ISO C plus K&R compatibility extensions, with semantic changes required by ISO C. This is the default mode if \fB-X\fR is not specified. The predefined macro \fB__STDC__\fR has a value of 0 when \fBcpp\fR is invoked in conjunction
-with the \fB-Xa\fR option.
+Default. ISO C plus K&R compatibility extensions, with semantic changes
+required by ISO C. This is the default mode if \fB-X\fR is not specified. The
+predefined macro \fB__STDC__\fR has a value of 0 when \fBcpp\fR is invoked in
+conjunction with the \fB-Xa\fR option.
 .RE
 
 .sp
@@ -488,7 +602,9 @@ with the \fB-Xa\fR option.
 .ad
 .RS 5n
 .rt  
-Conformance. Strictly conformant ISO C, without K&R C compatibility extensions. The predefined macro \fB__STDC__\fR has a value of 1 when \fBcpp\fR is invoked in conjunction with the \fB-Xc\fR option.
+Conformance. Strictly conformant ISO C, without K&R C compatibility extensions.
+The predefined macro \fB__STDC__\fR has a value of 1 when \fBcpp\fR is invoked
+in conjunction with the \fB-Xc\fR option.
 .RE
 
 .sp
@@ -499,7 +615,8 @@ Conformance. Strictly conformant ISO C, 
 .ad
 .RS 5n
 .rt  
-K&R C only. The macro \fB__STDC__\fR is not defined when \fBcpp\fR is invoked in conjunction with the \fB-Xs\fR option.
+K&R C only. The macro \fB__STDC__\fR is not defined when \fBcpp\fR is invoked
+in conjunction with the \fB-Xs\fR option.
 .RE
 
 .sp
@@ -510,12 +627,18 @@ K&R C only. The macro \fB__STDC__\fR is 
 .ad
 .RS 5n
 .rt  
-Transition. ISO C plus K&R C compatibility extensions, without semantic changes required by ISO C. The predefined macro \fB__STDC__\fR has a value of 0 when \fBcpp\fR is invoked in conjunction with the \fB-Xt\fR option.
+Transition. ISO C plus K&R C compatibility extensions, without semantic changes
+required by ISO C. The predefined macro \fB__STDC__\fR has a value of 0 when
+\fBcpp\fR is invoked in conjunction with the \fB-Xt\fR option.
 .RE
 
-As the \fB-X\fR option only affects how the D compiler invokes the C preprocessor, the \fB-Xa\fR and \fB-Xt\fR options are equivalent from the perspective of D and both are provided only to ease re-use of settings from a C build environment.
+As the \fB-X\fR option only affects how the D compiler invokes the C
+preprocessor, the \fB-Xa\fR and \fB-Xt\fR options are equivalent from the
+perspective of D and both are provided only to ease re-use of settings from a C
+build environment.
 .sp
-Regardless of the \fB-X\fR mode, the following additional C preprocessor definitions are always specified and valid in all modes:
+Regardless of the \fB-X\fR mode, the following additional C preprocessor
+definitions are always specified and valid in all modes:
 .RS +4
 .TP
 .ie t \(bu
@@ -576,8 +699,10 @@ Regardless of the \fB-X\fR mode, the fol
 .el o
 \fB__SUNW_D_VERSION=0x\fIMMmmmuuu\fR\fR
 .sp
-Where \fIMM\fR is the major release value in hexadecimal, \fImmm\fR is the minor release value in hexadecimal, and \fIuuu\fR is the
-micro release value in hexadecimal. Refer to the \fISolaris Dynamic Tracing Guide\fR for more information about DTrace versioning.
+Where \fIMM\fR is the major release value in hexadecimal, \fImmm\fR is the
+minor release value in hexadecimal, and \fIuuu\fR is the micro release value in
+hexadecimal. Refer to the \fISolaris Dynamic Tracing Guide\fR for more
+information about DTrace versioning.
 .RE
 .RE
 
@@ -589,14 +714,21 @@ micro release value in hexadecimal. Refe
 .ad
 .sp .6
 .RS 4n
-Permit probe descriptions that match zero probes. If the \fB-Z\fR option is not specified, \fBdtrace\fR reports an error and exits if any probe descriptions specified in D program files (\fB-s\fR option) or on the command line (\fB-P\fR, \fB-m\fR, \fB-f\fR, \fB-n\fR, or \fB-i\fR options) contain descriptions that do not match any known probes.
+Permit probe descriptions that match zero probes. If the \fB-Z\fR option is not
+specified, \fBdtrace\fR reports an error and exits if any probe descriptions
+specified in D program files (\fB-s\fR option) or on the command line
+(\fB-P\fR, \fB-m\fR, \fB-f\fR, \fB-n\fR, or \fB-i\fR options) contain
+descriptions that do not match any known probes.
 .RE
 
 .SH OPERANDS
 .sp
 .LP
-You can specify zero or more additional arguments on the \fBdtrace\fR command line to define a set of macro variables (\fB$1\fR, \fB$2\fR, and so forth). The additional arguments can be used in D programs specified using the \fB-s\fR option
-or on the command line. The use of macro variables is described further in the \fISolaris Dynamic Tracing Guide\fR.
+You can specify zero or more additional arguments on the \fBdtrace\fR command
+line to define a set of macro variables (\fB$1\fR, \fB$2\fR, and so forth). The
+additional arguments can be used in D programs specified using the \fB-s\fR
+option or on the command line. The use of macro variables is described further
+in the \fISolaris Dynamic Tracing Guide\fR.
 .SH EXIT STATUS
 .sp
 .LP
@@ -609,10 +741,12 @@ The following exit values are returned:
 .ad
 .RS 5n
 .rt  
-Successful completion. 
+Successful completion.
 .sp
-For D program requests, an exit status of \fB0\fR indicates that programs were successfully compiled, probes were successfully enabled, or anonymous state was successfully retrieved. \fBdtrace\fR returns \fB0\fR even if the specified tracing requests
-encountered errors or drops.
+For D program requests, an exit status of \fB0\fR indicates that programs were
+successfully compiled, probes were successfully enabled, or anonymous state was
+successfully retrieved. \fBdtrace\fR returns \fB0\fR even if the specified
+tracing requests encountered errors or drops.
 .RE
 
 .sp
@@ -625,7 +759,8 @@ encountered errors or drops.
 .rt  
 An error occurred.
 .sp
-For D program requests, an exit status of \fB1\fR indicates that program compilation failed or that the specified request could not be satisfied.
+For D program requests, an exit status of \fB1\fR indicates that program
+compilation failed or that the specified request could not be satisfied.
 .RE
 
 .sp
@@ -653,8 +788,6 @@ lw(2.75i) |lw(2.75i) 
 .
 ATTRIBUTE TYPEATTRIBUTE VALUE
 _
-AvailabilitySUNWdtrc
-_
 Interface StabilitySee below.
 .TE
 
@@ -664,7 +797,19 @@ The command-line syntax is Committed. Th
 .SH SEE ALSO
 .sp
 .LP
-\fBcpp\fR(1), \fBisainfo\fR(1), \fBlibdtrace\fR(3LIB), \fBdriver.conf\fR(4), \fBattributes\fR(5), \fBdtrace\fR(7D)
+\fBcpp\fR(1), \fBisainfo\fR(1), \fBssh\fR(1), \fBlibdtrace\fR(3LIB),
+\fBdriver.conf\fR(4), \fBattributes\fR(5), \fBdtrace\fR(7D)
 .sp
 .LP
 \fISolaris Dynamic Tracing Guide\fR
+.SH USAGE
+.sp
+.LP
+When using the \fB-p\fR flag, \fBdtrace\fR stops the target processes while it
+is inspecting them and reporting results. A process can do nothing while it is
+stopped. This means that, if , for example, the X server is inspected by
+\fBdtrace\fR running in a window under the X server's control, the whole window
+system can become deadlocked, because the \fBproc\fR tool would be attempting
+to display its results to a window that cannot be refreshed. In such a case,
+logging in from another system using \fBssh\fR(1) and killing the offending
+\fBproc\fR tool clears the deadlock.

Added: vendor/illumos/dist/man/man1m/lockstat.1m
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ vendor/illumos/dist/man/man1m/lockstat.1m	Wed Jul 18 09:53:20 2012	(r238581)
@@ -0,0 +1,909 @@
+'\" te
+.\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved.
+.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
+.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
+.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
+.TH lockstat 1M "28 Feb 2008" "SunOS 5.11" "System Administration Commands"
+.SH NAME
+lockstat \- report kernel lock and profiling statistics
+.SH SYNOPSIS
+.LP
+.nf
+\fBlockstat\fR [\fB-ACEHI\fR] [\fB-e\fR \fIevent_list\fR] [\fB-i\fR \fIrate\fR] 
+     [\fB-b\fR | \fB-t\fR | \fB-h\fR | \fB-s\fR \fIdepth\fR] [\fB-n\fR \fInrecords\fR] 
+     [\fB-l\fR \fIlock\fR [, \fIsize\fR]] [\fB-d\fR \fIduration\fR] 
+     [\fB-f\fR \fIfunction\fR [, \fIsize\fR]] [\fB-T\fR] [\fB-ckgwWRpP\fR] [\fB-D\fR \fIcount\fR] 
+     [\fB-o\fR \fIfilename\fR] [\fB-x\fR \fIopt\fR [=val]] \fIcommand\fR [\fIargs\fR]
+.fi
+
+.SH DESCRIPTION
+.sp
+.LP
+The \fBlockstat\fR utility gathers and displays kernel locking and profiling
+statistics. \fBlockstat\fR allows you to specify which events to watch (for
+example, spin on adaptive mutex, block on read access to rwlock due to waiting
+writers, and so forth) how much data to gather for each event, and how to
+display the data. By default, \fBlockstat\fR monitors all lock contention
+events, gathers frequency and timing data about those events, and displays the
+data in decreasing frequency order, so that the most common events appear
+first.
+.sp
+.LP
+\fBlockstat\fR gathers data until the specified command completes. For example,
+to gather statistics for a fixed-time interval, use \fBsleep\fR(1) as the
+command, as follows:
+.sp
+.LP
+\fBexample#\fR \fBlockstat\fR \fBsleep\fR \fB5\fR
+.sp
+.LP
+When the \fB-I\fR option is specified, \fBlockstat\fR establishes a
+per-processor high-level periodic interrupt source to gather profiling data.
+The interrupt handler simply generates a \fBlockstat\fR event whose caller is
+the interrupted PC (program counter). The profiling event is just like any
+other \fBlockstat\fR event, so all of the normal \fBlockstat\fR options are
+applicable.
+.sp
+.LP
+\fBlockstat\fR relies on DTrace to modify the running kernel's text to
+intercept events of interest. This imposes a small but measurable overhead on
+all system activity, so access to \fBlockstat\fR is restricted to super-user by
+default. The system administrator can permit other users to use \fBlockstat\fR
+by granting them additional DTrace privileges. Refer to the \fISolaris Dynamic
+Tracing Guide\fR for more information about DTrace security features.
+.SH OPTIONS
+.sp
+.LP
+The following options are supported:
+.SS "Event Selection"
+.sp
+.LP
+If no event selection options are specified, the default is \fB-C\fR.
+.sp
+.ne 2
+.mk
+.na
+\fB\fB-A\fR\fR
+.ad
+.sp .6
+.RS 4n
+Watch all lock events. \fB-A\fR is equivalent to \fB-CH\fR.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB-C\fR\fR
+.ad
+.sp .6
+.RS 4n
+Watch contention events.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB-E\fR\fR
+.ad
+.sp .6
+.RS 4n
+Watch error events.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB\fR\fB-e\fR \fIevent_list\fR\fR
+.ad
+.sp .6
+.RS 4n
+Only watch the specified events. \fIevent\fR \fIlist\fR is a comma-separated
+list of events or ranges of events such as 1,4-7,35. Run \fBlockstat\fR with no
+arguments to get a brief description of all events.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB-H\fR\fR
+.ad
+.sp .6
+.RS 4n
+Watch hold events.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB-I\fR\fR
+.ad
+.sp .6
+.RS 4n
+Watch profiling interrupt events.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB\fR\fB-i\fR \fIrate\fR\fR
+.ad
+.sp .6
+.RS 4n
+Interrupt rate (per second) for \fB-I\fR. The default is 97 Hz, so that
+profiling doesn't run in lockstep with the clock interrupt (which runs at 100
+Hz).
+.RE
+
+.SS "Data Gathering"
+.sp
+.ne 2
+.mk
+.na
+\fB\fB-x\fR \fIarg\fR[=\fIval\fR]\fR
+.ad
+.sp .6
+.RS 4n
+Enable or modify a DTrace runtime option or D compiler option. The list of
+options is found in the \fI\fR. Boolean options are enabled by specifying their
+name. Options with values are set by separating the option name and value with
+an equals sign (=).
+.RE
+
+.SS "Data Gathering (Mutually Exclusive)"
+.sp
+.ne 2
+.mk
+.na
+\fB\fB-b\fR\fR
+.ad
+.sp .6
+.RS 4n
+Basic statistics: lock, caller, number of events.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB-h\fR\fR
+.ad
+.sp .6
+.RS 4n
+Histogram: Timing plus time-distribution histograms.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB\fR\fB-s\fR \fIdepth\fR\fR
+.ad
+.sp .6
+.RS 4n
+Stack trace: Histogram plus stack traces up to \fIdepth\fR frames deep.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB-t\fR\fR
+.ad
+.sp .6
+.RS 4n
+Timing: Basic plus timing for all events [default].
+.RE
+
+.SS "Data Filtering"
+.sp
+.ne 2
+.mk
+.na
+\fB\fB\fR\fB-d\fR \fIduration\fR\fR
+.ad
+.sp .6
+.RS 4n
+Only watch events longer than \fIduration\fR.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB\fR\fB-f\fR \fIfunc[,size]\fR\fR
+.ad
+.sp .6
+.RS 4n
+Only watch events generated by \fIfunc\fR, which can be specified as a symbolic
+name or hex address. \fIsize\fR defaults to the \fBELF\fR symbol size if
+available, or \fB1\fR if not.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB\fR\fB-l\fR \fIlock[,size]\fR\fR
+.ad
+.sp .6
+.RS 4n
+Only watch \fIlock\fR, which can be specified as a symbolic name or hex
+address. \fBsize\fR defaults to the \fBELF\fR symbol size or \fB1\fR if the
+symbol size is not available.
+.RE
+
+.sp
+.ne 2
+.mk
+.na
+\fB\fB\fR\fB-n\fR \fInrecords\fR\fR
+.ad
+.sp .6
+.RS 4n
+Maximum number of data records.
+.RE
+
+.sp
+.ne 2
+.mk
+.na

*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201207180953.q6I9rLQF052608>