src/sys/modules/dtrace/Makefile, branch release/9.3.0

followup to r260816, MFC of r257037: remove dtio from dtrace Makefile

2014-01-17T15:01:50Z

svn merge ran without any complains or errors, but this Makefile somehow was not updated. This is a direct commit. Reported by: Jukka Ukkonen

MFC: 238366, 240924

2012-12-07T19:06:40Z

Initial commit of an I/O provider for DTrace on FreeBSD. These probes are most useful when looking into the structures they provide, which are listed in io.d. For example: dtrace -n 'io:kernel::start { printf("%d\n", args[0]->bio_bcount); }' Note that the I/O systems in FreeBSD and Solaris/Illumos are sufficiently different that there is not a 1:1 mapping from scripts that work with one to the other. This commit includes the fix so that our probes use "kernel" instead of the Solaris specific "genunix"

Add DTrace support to the new NFS client. This is essentially

2011-06-18T23:02:53Z

cloned from the old NFS client, plus additions for NFSv4. A review of this code is in progress, however it was felt by the reviewer that it could go in now, before code slush. Any changes required by the review can be committed as bug fixes later.

add DTrace systrace support for linux32 and freebsd32 on amd64 syscalls

2011-03-12T09:09:25Z

Add systrace_linux32 and systrace_freebsd32 modules which provide support for tracing compat system calls in addition to native system call tracing provided by systrace module. Provided that all the systrace modules are loaded now you can select what syscalls to trace in the following manner: syscall::xxx:yyy - work on all system calls that match the specification syscall:freebsd:xxx:yyy - only native system calls syscall:linux32:xxx:yyy - linux32 compat system calls syscall:freebsd32:xxx:yyy - freebsd32 compat system calls on amd64 PR: kern/152822 Submitted by: Artem Belevich Reviewed by: jhb (earlier version) MFC after: 3 weeks

Enable fasttrap and make dtraceall depend on fasttrap when building i386

2010-08-24T13:21:05Z

or amd64. Sponsored by: The FreeBSD Foundation

MFtbemd:

2010-08-23T06:13:29Z

Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed...

Remove an elif and add an or-clause.

2010-08-22T11:12:07Z

Add the OpenSolaris dtrace lockstat provider. The lockstat provider

2009-05-26T20:28:22Z

adds probes for mutexes, reader/writer and shared/exclusive locks to gather contention statistics and other locking information for dtrace scripts, the lockstat(1M) command and other potential consumers. Reviewed by: attilio jhb jb Approved by: gnn (mentor)

Add dtnfsclient, a first cut at an NFSv2/v3 client reuest DTrace

2009-03-22T22:07:52Z

provider. The NFS client exposes 'start' and 'done' probes for NFSv2 and NFSv3 RPCs when using the new RPC implementation, passing in the vnode, mbuf chain, credential, and NFSv2 or NFSv3 procedure number. For 'done' probes, the error number is also available. Probes are named in the following way: ... nfsclient:nfs2:write:start nfsclient:nfs2:write:done ... nfsclient:nfs3:access:start nfsclient:nfs3:access:done ... Access to the unmarshalled arguments is not easily available at this point in the stack, but the passed probe arguments are sufficient to to a lot of interesting things in practice. Technically, these probes may cover multiple RPC retransmits, and even transactions if the transaction ID change as a result of authentication failure or a jukebox error from the server, but usefully capture the intent of a single NFS request, such as access, getattr, write, etc. Typical use might involve profiling RPC latency by system call, number of RPCs, how often a getattr leads to a call to access, when failed access control checks occur, etc. More detailed RPC information might best be provided by adding a krpc provider. It would also be useful to add NFS client probes for events such as the access cache or attribute cache satisfying requests without an RPC. Sponsored by: Google, Inc. MFC after: 1 month

Add the DTrace test kernel module so that people can run the tests.

2008-05-31T09:37:40Z